mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-25 05:34:00 +08:00
ad0b314e00
Pull sysctl system call removal from Eric Biederman: "As far as I can tell we have reached the point where no one enables the sysctl system call anymore. It still is enabled in a few defconfigs but they are mostly the rarely used one and in asking people about that it was more cut & paste enabled than anything else. This is single commit that just deletes code. Leaving just enough code so that the deprecated sysctl warning continues to be printed. If my analysis turns out to be wrong and someone actually cares it will be easy to revert this commit and have the system call again. There was one new xtensa defconfig in linux-next that enabled the system call this cycle and when asked about it the maintainer of the code replied that it was not enabled on purpose. As of today's linux-next tree that defconfig no longer enables the system call. What we saw in the review discussion was that if we go a step farther than my patch and mess with uapi headers there are pieces of code that won't compile, but nothing minds the system call actually disappearing from the kernel" Link: https://lore.kernel.org/lkml/201910011140.EA0181F13@keescook/ * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace: sysctl: Remove the sysctl system call |
||
|---|---|---|
| .. | ||
| amcore_defconfig | ||
| amiga_defconfig | ||
| apollo_defconfig | ||
| atari_defconfig | ||
| bvme6000_defconfig | ||
| hp300_defconfig | ||
| m5208evb_defconfig | ||
| m5249evb_defconfig | ||
| m5272c3_defconfig | ||
| m5275evb_defconfig | ||
| m5307c3_defconfig | ||
| m5407c3_defconfig | ||
| m5475evb_defconfig | ||
| mac_defconfig | ||
| multi_defconfig | ||
| mvme16x_defconfig | ||
| mvme147_defconfig | ||
| q40_defconfig | ||
| stmark2_defconfig | ||
| sun3_defconfig | ||
| sun3x_defconfig | ||