From: Miklos Szeredi <miklos@szeredi.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] fuse fixes for 4.20-rc3
Date: Thu, 15 Nov 2018 20:58:52 +0100 [thread overview]
Message-ID: <20181115195852.GA5245@veci.piliscsaba.redhat.com> (raw)
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git tags/fuse-fixes-4.20-rc3
A couple of fixes, all bound for -stable (i.e. not regressions in this
cycle).
Thanks,
Miklos
----------------------------------------------------------------
Lukas Czerner (1):
fuse: fix use-after-free in fuse_direct_IO()
Miklos Szeredi (2):
fuse: fix leaked notify reply
fuse: fix possibly missed wake-up after abort
---
fs/fuse/dev.c | 16 ++++++++++++----
fs/fuse/file.c | 4 +++-
2 files changed, 15 insertions(+), 5 deletions(-)
next reply other threads:[~2018-11-15 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 19:58 Miklos Szeredi [this message]
2018-11-16 16:25 ` [GIT PULL] fuse fixes for 4.20-rc3 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=20181115195852.GA5245@veci.piliscsaba.redhat.com \
--to=miklos@szeredi.hu \
--cc=linux-fsdevel@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 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).