From: Al Viro <viro@ZenIV.linux.org.uk>
To: Enrico Weigelt <lkml@metux.net>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: fs_struct refcounting: spinlock vs atomic
Date: Thu, 15 Feb 2018 18:52:04 +0000 [thread overview]
Message-ID: <20180215185204.GD30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20180215183956.GC30522@ZenIV.linux.org.uk>
On Thu, Feb 15, 2018 at 06:39:57PM +0000, Al Viro wrote:
> Not true. We also assume that once fs_struct has been locked, the number of
> tasks with reference to it won't change. See fs/exec.c:check_unsafe_exec(),
> for example.
PS: any discussion of VFS and filesystems stuff belongs on fsdevel; Cc to l-k
is fine, but don't expect anyone to be able to reliably spot it there.
l-k is far too high volume (and low S/N) to keep up with it; some of us have
entirely given up on it (Linus is certainly not the only one who'd unsubscribed
from l-k many years ago), some try to scan it for something relevant, but
latency and reliability of such scans inevitably sucks.
prev parent reply other threads:[~2018-02-15 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 21:13 fs_struct refcounting: spinlock vs atomic Enrico Weigelt
2018-02-15 9:14 ` Richard Weinberger
2018-02-15 13:46 ` Enrico Weigelt
2018-02-15 18:39 ` Al Viro
2018-02-15 18:52 ` Al Viro [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=20180215185204.GD30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=richard.weinberger@gmail.com \
/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