From: Christoph Hellwig <hch@infradead.org>
To: David Chen <david.chen@osnexus.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
lkml <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] vfs: check i_count under lock in evict_inodes
Date: Mon, 11 Jul 2016 18:40:25 -0700 [thread overview]
Message-ID: <20160712014025.GA23449@infradead.org> (raw)
In-Reply-To: <CAK1sfubpLBv3P5ttpuq1z+EyNGHFiiMEVLSCv5HoQ51f_pFHig@mail.gmail.com>
On Mon, Jul 11, 2016 at 06:31:57PM -0700, David Chen wrote:
> Hi Al,
>
> I'm not sure about the in-tree fs, but in zfsonlinux, it would offload
> iput to a thread, so this would happen there. And it would wait for
> the thread in put_super(), so that part is not a problem...
And why exactly is your use of a broken and undistributable out of tree
module our problem?
next prev parent reply other threads:[~2016-07-12 1:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 0:15 [PATCH] vfs: check i_count under lock in evict_inodes Chunwei Chen
2016-07-12 0:46 ` Al Viro
2016-07-12 1:31 ` David Chen
2016-07-12 1:40 ` Christoph Hellwig [this message]
2016-07-12 5:26 ` Al Viro
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=20160712014025.GA23449@infradead.org \
--to=hch@infradead.org \
--cc=david.chen@osnexus.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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).