From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] fsnotify fix for v5.1-rc8
Date: Tue, 30 Apr 2019 23:41:49 +0200 [thread overview]
Message-ID: <20190430214149.GA482@quack2.suse.cz> (raw)
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git fsnotify_for_v5.1-rc8
to get a fix of user trigerable NULL pointer dereference syzbot has
recently spotted. The problem has been introduced in rc1 so no CC stable is
needed.
Top of the tree is b1da6a51871c. The full shortlog is:
Jan Kara (1):
fsnotify: Fix NULL ptr deref in fanotify_get_fsid()
The diffstat is
fs/notify/fanotify/fanotify.c | 14 ++++++++++++--
fs/notify/mark.c | 12 ++++++------
2 files changed, 18 insertions(+), 8 deletions(-)
Also I'm sorry but the tag is not signed as I'm at LSF/MM this week and
forgot my Yubikey at home...
Thanks
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next reply other threads:[~2019-04-30 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 21:41 Jan Kara [this message]
2019-04-30 22:10 ` [GIT PULL] fsnotify fix for v5.1-rc8 Linus Torvalds
2019-05-01 14:52 ` Jan Kara
2019-05-01 15:34 ` Jan Kara
2019-04-30 22:30 ` 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=20190430214149.GA482@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).