[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240730071851.GE5334@ZenIV>
Date: Tue, 30 Jul 2024 08:18:51 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: Michal Hocko <mhocko@...e.com>
Cc: viro@...nel.org, linux-fsdevel@...r.kernel.org, amir73il@...il.com,
bpf@...r.kernel.org, brauner@...nel.org, cgroups@...r.kernel.org,
kvm@...r.kernel.org, netdev@...r.kernel.org,
torvalds@...ux-foundation.org
Subject: Re: [PATCH 01/39] memcg_write_event_control(): fix a
user-triggerable oops
On Tue, Jul 30, 2024 at 09:13:38AM +0200, Michal Hocko wrote:
> On Tue 30-07-24 01:15:47, viro@...nel.org wrote:
> > From: Al Viro <viro@...iv.linux.org.uk>
> >
> > we are *not* guaranteed that anything past the terminating NUL
> > is mapped (let alone initialized with anything sane).
> >
> > [the sucker got moved in mainline]
> >
>
> You could have preserved
> Fixes: 0dea116876ee ("cgroup: implement eventfd-based generic API for notifications")
> Cc: stable
>
> > Signed-off-by: Al Viro <viro@...iv.linux.org.uk>
>
> and
> Acked-by: Michal Hocko <mhocko@...e.com>
Will do; FWIW, I think it would be better off going via the
cgroup tree - it's completely orthogonal to the rest of the
series, the only relation being "got caught during the same
audit"...
Powered by blists - more mailing lists