FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F11.3.0 2018-03-29T02:50:57Z 2018-03-29T02:50:57Z Eitan Adler eadler@FreeBSD.org 2018-03-29T02:50:57Z urn:sha1:4ab2e064d7950be84256d671a7ae93f87cc6aa36 This was intended to be a non-functional change. It wasn't. The commit message was thus wrong. In addition it broke arm, and merged crypto related code. Revert with prejudice. This revert skips files touched in r316370 since that commit was since MFCed. This revert also skips files that require $FreeBSD$ property changes. Thank you to those who helped me get out of this mess including but not limited to gonzo, kevans, rgrimes. Requested by: gjb (re) 2018-03-14T03:19:51Z Eitan Adler eadler@FreeBSD.org 2018-03-14T03:19:51Z urn:sha1:be5d0b9566b13fdf8cabebb63334cbec12bfc409 These changes are incomplete but are making it difficult to determine what other changes can/should be merged. No objections from: pfg 2014-11-11T04:48:09Z Pawel Jakub Dawidek pjd@FreeBSD.org 2014-11-11T04:48:09Z urn:sha1:5ebb15b942bfe98b9b972117ecb04e97de8cb947 was possible for a regular user to setup the dump device if he had write access to the given device. In theory it is a security issue as user might get access to kernel's memory after provoking kernel crash, but in practise it is not recommended to give regular users direct access to storage devices. Rework the code so that we do privileges check within the set_dumper() function to avoid similar problems in the future. Discussed with: secteam 2014-04-30T06:40:30Z Eitan Adler eadler@FreeBSD.org 2014-04-30T06:40:30Z urn:sha1:9ca1db6598eceb5d72c06bc569d6fed45ca28abe Mark another parameter as unused Reported by: rpaulo 2014-04-30T06:30:37Z Eitan Adler eadler@FreeBSD.org 2014-04-30T06:30:37Z urn:sha1:7a07ae0a8ed30a42fd216efd898913b9d9d4b911 Use a consistent ordering of full -> null -> zero (alphabetical) in null.c Reported by: mjg 2014-04-30T06:20:48Z Eitan Adler eadler@FreeBSD.org 2014-04-30T06:20:48Z urn:sha1:a345aa595359db9cd3443476c58a27de1adfbab0 /dev/full is similar to /dev/zero except it always returns ENOSPC when you attempt to write to it. Reviewed by: jhibbits Discussed with: rpaulo 2012-11-01T17:01:05Z Alfred Perlstein alfred@FreeBSD.org 2012-11-01T17:01:05Z urn:sha1:bad7e7f3dd67f666fcef8032b2a6e46d38e06012 state of crashdump target devices. This will be used to add a "-l" (ell) flag to dumpon(8) to list the currently configured dumpdev. Reviewed by: phk 2012-01-11T15:00:16Z George V. Neville-Neil gnn@FreeBSD.org 2012-01-11T15:00:16Z urn:sha1:844d43d94b0e0380a8b6c29982c0783a590f734b Add the ability for /dev/null and /dev/zero to accept being set into non blocking mode via fcntl(). This brings the code into compliance with IEEE Std 1003.1-2001 as referenced in another PR, 94729. Reviewed by: jhb MFC after: 1 week 2011-05-13T19:35:01Z Matthew D Fleming mdf@FreeBSD.org 2011-05-13T19:35:01Z urn:sha1:cfb00e5aa764c1f87067cd819c7ab378f3d11a77 architectures (i386, for example) the virtual memory space may be constrained enough that 2MB is a large chunk. Use 64K for arches other than amd64 and ia64, with special handling for sparc64 due to differing hardware. Also commit the comment changes to kmem_init_zero_region() that I missed due to not saving the file. (Darn the unfamiliar development environment). Arch maintainers, please feel free to adjust ZERO_REGION_SIZE as you see fit. Requested by: alc MFC after: 1 week MFC with: r221853 2011-05-13T18:48:00Z Matthew D Fleming mdf@FreeBSD.org 2011-05-13T18:48:00Z urn:sha1:89cb2a19ec7be4fe31ba6463ecda4c16ea748afe device. There are likely other kernel uses of "blob of zeros" than can be converted. Reviewed by: alc MFC after: 1 week