From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dave Chinner <david@fromorbit.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
Byungchul Park <byungchul.park@lge.com>,
Theodore Ts'o <tytso@mit.edu>, fstests <fstests@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
mingo@redhat.com, kernel-team@lge.com
Subject: Re: False lockdep completion splats with loop device
Date: Fri, 8 Dec 2017 00:13:02 +0000 [thread overview]
Message-ID: <20171208001302.GK21978@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20171207235922.GJ5858@dastard>
On Fri, Dec 08, 2017 at 10:59:22AM +1100, Dave Chinner wrote:
> > 3. if multi nested looped fs is important (not really) then loop/nbd will
> > need to know if its file is on a looped fs and propagate nesting level
> > to ext4
>
> This functionality is definitely used and needs to be supported by
> the annotations.
FWIW, in addition to loop, there's md. So should loop need to know if its
backing file lives on a filesystem that does, for example, have an extrnal
journal sitting on RAID1 with one of the components hosted in a file on
some other fs, brought into the array via another loop device?
Oh, and to make life even more fun, backing file can be flipped under
configured /dev/loop. IOW, those nesting depths are not static at all.
next prev parent reply other threads:[~2017-12-08 0:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 3:03 False lockdep completion splats with loop device Theodore Ts'o
2017-12-05 5:16 ` Byungchul Park
2017-12-05 15:07 ` Theodore Ts'o
2017-12-05 21:09 ` Dave Chinner
2017-12-06 5:01 ` Byungchul Park
2017-12-06 6:08 ` Dave Chinner
2017-12-06 6:31 ` Amir Goldstein
2017-12-06 7:01 ` Byungchul Park
2017-12-07 2:46 ` Amir Goldstein
2017-12-07 4:18 ` Amir Goldstein
2017-12-07 14:33 ` Theodore Ts'o
2017-12-07 14:53 ` Peter Zijlstra
2017-12-08 1:51 ` Byungchul Park
2017-12-07 23:59 ` Dave Chinner
2017-12-08 0:13 ` Al Viro [this message]
2017-12-08 8:15 ` Amir Goldstein
2017-12-08 22:57 ` Dave Chinner
2017-12-09 8:44 ` Amir Goldstein
2017-12-09 16:02 ` Theodore Ts'o
2017-12-09 20:08 ` Amir Goldstein
2017-12-06 6:23 ` Byungchul Park
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=20171208001302.GK21978@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=amir73il@gmail.com \
--cc=byungchul.park@lge.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=kernel-team@lge.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tytso@mit.edu \
/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).