From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org
Subject: [git pull] vfs.git memcontrol oops fix
Date: Sat, 17 Aug 2024 00:40:44 +0100 [thread overview]
Message-ID: <20240816234044.GG504335@ZenIV> (raw)
The following changes since commit 9a2fa1472083580b6c66bdaf291f591e1170123a:
fix bitmap corruption on close_range() with CLOSE_RANGE_UNSHARE (2024-08-05 19:23:11 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fixes
for you to fetch changes up to 046667c4d3196938e992fba0dfcde570aa85cd0e:
memcg_write_event_control(): fix a user-triggerable oops (2024-08-12 21:58:44 -0400)
----------------------------------------------------------------
memcg_write_event_control() oops fix
----------------------------------------------------------------
Al Viro (1):
memcg_write_event_control(): fix a user-triggerable oops
mm/memcontrol-v1.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
next reply other threads:[~2024-08-16 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 23:40 Al Viro [this message]
2024-08-17 0:15 ` [git pull] vfs.git memcontrol oops fix pr-tracker-bot
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=20240816234044.GG504335@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.