From: Tycho Andersen <tycho@tycho.pizza>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Oleg Nesterov <oleg@redhat.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
Miklos Szeredi <miklos@szeredi.hu>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH v2] fuse: In fuse_flush only wait if someone wants the return code
Date: Mon, 15 Aug 2022 07:59:08 -0600 [thread overview]
Message-ID: <YvpRLJ79GRWYjLdf@tycho.pizza> (raw)
In-Reply-To: <875yjfdw3a.fsf_-_@email.froward.int.ebiederm.org>
Hi,
On Sat, Jul 30, 2022 at 12:10:33AM -0500, Eric W. Biederman wrote:
> Al, vfs folks? (igrab/iput sorted so as not to be distractions).
Any movement on this? Can you resend (or I can) the patch with the
fixes for fuse at the very least?
Thanks,
next prev parent reply other threads:[~2022-08-15 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YuFdUj5X4qckC/6g@tycho.pizza>
[not found] ` <20220727175538.GC18822@redhat.com>
[not found] ` <YuGBXnqb5rPwAlYk@tycho.pizza>
[not found] ` <20220727191949.GD18822@redhat.com>
[not found] ` <YuGUyayVWDB7R89i@tycho.pizza>
[not found] ` <20220728091220.GA11207@redhat.com>
[not found] ` <YuL9uc8WfiYlb2Hw@tycho.pizza>
[not found] ` <87pmhofr1q.fsf@email.froward.int.ebiederm.org>
[not found] ` <YuPlqp0jSvVu4WBK@tycho.pizza>
[not found] ` <87v8rfevz3.fsf@email.froward.int.ebiederm.org>
[not found] ` <YuQPc51yXhnBHjIx@tycho.pizza>
2022-07-29 17:40 ` [RFC][PATCH] fuse: In fuse_flush only wait if someone wants the return code Eric W. Biederman
2022-07-29 20:47 ` Oleg Nesterov
2022-07-30 0:15 ` Al Viro
2022-07-30 5:10 ` [RFC][PATCH v2] " Eric W. Biederman
2022-08-01 15:16 ` Tycho Andersen
2022-08-02 12:50 ` Miklos Szeredi
2022-08-15 13:59 ` Tycho Andersen [this message]
2022-08-15 17:55 ` Serge E. Hallyn
2022-09-19 15:46 ` Eric W. Biederman
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=YvpRLJ79GRWYjLdf@tycho.pizza \
--to=tycho@tycho.pizza \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=oleg@redhat.com \
--cc=serge@hallyn.com \
--cc=viro@zeniv.linux.org.uk \
/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).