From: Al Viro <viro@zeniv.linux.org.uk>
To: Michal Hocko <mhocko@suse.com>
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memcg_write_event_control(): fix a user-triggerable oops
Date: Fri, 26 Jul 2024 08:48:04 +0100 [thread overview]
Message-ID: <20240726074804.GE99483@ZenIV> (raw)
In-Reply-To: <ZqNMfL6JmgHCJwBv@tiehlicka>
On Fri, Jul 26, 2024 at 09:13:00AM +0200, Michal Hocko wrote:
> On Fri 26-07-24 09:06:59, Michal Hocko wrote:
> > On Fri 26-07-24 06:43:57, Al Viro wrote:
> > > We are *not* guaranteed that anything past the terminating NUL
> > > is mapped (let alone initialized with anything sane).
> > >
> >
> > Fixes: 0dea116876ee ("cgroup: implement eventfd-based generic API for notifications")
> >
> > > Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> >
> > Acked-by: Michal Hocko <mhocko@suse.com>
>
> Btw. this should be
> Cc: stable
Point, except that for -stable it needs to be applied to mm/memcontrol.c
instead...
next prev parent reply other threads:[~2024-07-26 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 5:43 [PATCH] memcg_write_event_control(): fix a user-triggerable oops Al Viro
2024-07-26 7:06 ` Michal Hocko
2024-07-26 7:13 ` Michal Hocko
2024-07-26 7:48 ` Al Viro [this message]
2024-07-26 7:54 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240726074804.GE99483@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox