Messages in this thread | | | Date | Mon, 8 Apr 2013 14:34:38 -0700 | Subject | Re: [PATCH] kmsg: Honor dmesg_restrict sysctl on /dev/kmsg | From | Kees Cook <> |
| |
On Mon, Apr 1, 2013 at 6:05 PM, Josh Boyer <jwboyer@redhat.com> wrote: > ----- Original Message ----- >> From: "Kees Cook" <keescook@chromium.org> >> To: "Josh Boyer" <jwboyer@redhat.com> >> Cc: "Andrew Morton" <akpm@linux-foundation.org>, "Eric Paris" <eparis@redhat.com>, "Linus Torvalds" >> <torvalds@linux-foundation.org>, "Christian Kujau" <lists@nerdbynature.de>, "# 3.4.x" <stable@vger.kernel.org>, >> "LKML" <linux-kernel@vger.kernel.org> >> Sent: Monday, April 1, 2013 7:51:57 PM >> Subject: Re: [PATCH] kmsg: Honor dmesg_restrict sysctl on /dev/kmsg >> >> On Fri, Mar 22, 2013 at 3:14 PM, Josh Boyer <jwboyer@redhat.com> wrote: >> > On Fri, Mar 22, 2013 at 02:54:48PM -0700, Andrew Morton wrote: >> >> >> >> poke. Nothing got applied. I'll drop >> >> kmsg-honor-dmesg_restrict-sysctl-on-dev-kmsg.patch, see if that has any >> >> effect ;) >> > >> > Oh dear. >> > >> > Eric, were you going to cleanup your suggestion and send it out? >> >> Ping? What state is this in? > > If Eric doesn't send a patch tomorrow, I will. Fedora is carrying my > original patch, but I'd rather get this fixed everywhere.
Pinging again here. Any news on this?
-Kees
-- Kees Cook Chrome OS Security
| |