Re: [PATCH AUTOSEL for 4.9 188/293] fs: warn in case userspace lied about modprobe return

On Sun, Apr 8, 2018 at 5:25 PM, Sasha Levin wrote: > From: "Luis R. Rodriguez" > > [ Upstream commit 41124db869b7e00e12052555f8987867ac01d70c ] > > kmod <= v19 was broken -- it could return 0 to modprobe calls, > incorrectly assuming that a

Re: [PATCH AUTOSEL for 4.9 188/293] fs: warn in case userspace lied about modprobe return

On Sun, Apr 8, 2018 at 5:25 PM, Sasha Levin wrote: > From: "Luis R. Rodriguez" > > [ Upstream commit 41124db869b7e00e12052555f8987867ac01d70c ] > > kmod <= v19 was broken -- it could return 0 to modprobe calls, > incorrectly assuming that a kernel module was built-in, whereas in > reality the

[PATCH AUTOSEL for 4.9 188/293] fs: warn in case userspace lied about modprobe return

From: "Luis R. Rodriguez" [ Upstream commit 41124db869b7e00e12052555f8987867ac01d70c ] kmod <= v19 was broken -- it could return 0 to modprobe calls, incorrectly assuming that a kernel module was built-in, whereas in reality the module was just forming in the kernel. The

[PATCH AUTOSEL for 4.9 188/293] fs: warn in case userspace lied about modprobe return

From: "Luis R. Rodriguez" [ Upstream commit 41124db869b7e00e12052555f8987867ac01d70c ] kmod <= v19 was broken -- it could return 0 to modprobe calls, incorrectly assuming that a kernel module was built-in, whereas in reality the module was just forming in the kernel. The reason for this is an