From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: chadaustin@fb.com, mszeredi@redhat.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns" failed to apply to 4.9-stable tree
Date: Tue, 18 Dec 2018 16:59:06 -0500 [thread overview]
Message-ID: <20181218215906.GH2746@sasha-vm> (raw)
In-Reply-To: <1545145239105238@kroah.com>
On Tue, Dec 18, 2018 at 04:00:39PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.9-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>>From 2e64ff154ce6ce9a8dc0f9556463916efa6ff460 Mon Sep 17 00:00:00 2001
>From: Chad Austin <chadaustin@fb.com>
>Date: Mon, 10 Dec 2018 10:54:52 -0800
>Subject: [PATCH] fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns
> ENOSYS
>
>When FUSE_OPEN returns ENOSYS, the no_open bit is set on the connection.
>
>Because the FUSE_RELEASE and FUSE_RELEASEDIR paths share code, this
>incorrectly caused the FUSE_RELEASEDIR request to be dropped and never sent
>to userspace.
>
>Pass an isdir bool to distinguish between FUSE_RELEASE and FUSE_RELEASEDIR
>inside of fuse_file_put.
>
>Fixes: 7678ac50615d ("fuse: support clients that don't implement 'open'")
>Cc: <stable@vger.kernel.org> # v3.14
>Signed-off-by: Chad Austin <chadaustin@fb.com>
>Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
On older kernels this patch depends on the following two:
9a87ad3da905 fuse: release: private_data cannot be NULL
267d84449f52 fuse: cleanup fuse_file refcounting
But I'm not sure about taking them as is.
--
Thanks,
Sasha
prev parent reply other threads:[~2018-12-18 21:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 15:00 FAILED: patch "[PATCH] fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns" failed to apply to 4.9-stable tree gregkh
2018-12-18 21:59 ` Sasha Levin [this message]
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=20181218215906.GH2746@sasha-vm \
--to=sashal@kernel.org \
--cc=chadaustin@fb.com \
--cc=gregkh@linuxfoundation.org \
--cc=mszeredi@redhat.com \
--cc=stable@vger.kernel.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).