[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAB=NE6WaQqp52MfZfjcShAUchj-1B+ZMsF1r6HabSiUxFLb7jQ@mail.gmail.com>
Date: Thu, 14 Aug 2014 22:48:05 -0400
From: "Luis R. Rodriguez" <mcgrof@...not-panic.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: "Luis R. Rodriguez" <mcgrof@...not-panic.com>,
Al Viro <viro@...iv.linux.org.uk>, Chris Mason <clm@...com>,
jbacik@...com, linux-fsdevel@...r.kernel.org,
linux-btrfs@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jeff Mahoney <jeffm@...e.com>, fdmanana@...e.com
Subject: Re: [RFC v2 0/2] vfs / btrfs: add support for ustat()
On Thu, Jul 17, 2014 at 1:49 PM, Luis R. Rodriguez <mcgrof@...e.com> wrote:
> On Thu, Jul 17, 2014 at 01:03:01AM -0700, Christoph Hellwig wrote:
>> On Wed, Jul 16, 2014 at 02:37:56PM -0700, Luis R. Rodriguez wrote:
>> > From: "Luis R. Rodriguez" <mcgrof@...e.com>
>> >
>> > This makes the implementation simpler by stuffing the struct on
>> > the driver and just letting the driver iinsert it and remove it
>> > onto the sb list. This avoids the kzalloc() completely.
>>
>> Again, NAK. Make btrfs report the proper anon dev_t in stat and
>> everything will just work.
>
> Let's consider this userspace case:
>
> struct stat buf;
> struct ustat ubuf;
>
> /* Find a valid device number */
> if (stat("/", &buf)) {
> fprintf(stderr, "Stat failed: %s\n", strerror(errno));
> return 1;
> }
>
> /* Call ustat on it */
> if (ustat(buf.st_dev, &ubuf)) {
> fprintf(stderr, "Ustat failed: %s\n", strerror(errno));
> return 1;
> }
>
> In the btrfs case it has an inode op for getattr, that is used and we set
> the dev to anonymous dev_t. Later ustat will use user_get_super() which
> will only be able to work with a userblock if the super block's only
> dev_t is assigned to it. Since we have many anonymous to dev_t mapping
> to super block though we can't complete the search for btfs and ustat()
> fails with -EINVAL. The series expands the number of dev_t's that a super
> block can have and allows this search to complete.
Any further advice? I'll submit a v3 for RFC with some small change
for a fix for stress testing identified by Filipe Manana.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists