[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110418230254.GA22588@redhat.com>
Date: Mon, 18 Apr 2011 19:02:55 -0400
From: Dave Jones <davej@...hat.com>
To: Kay Sievers <kay.sievers@...y.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Eric Sandeen <sandeen@...hat.com>
Subject: Re: Linux 2.6.39-rc3
On Tue, Apr 19, 2011 at 12:57:27AM +0200, Kay Sievers wrote:
> > uuid:<value> is the option field as per
> > Documentation/filesystem/proc.txt. There was an error in libmount
> > parsing which got fixed upstream recently
>
> Just a simple question about this approach in general? A filesystem
> UUID can be changed on disk at any time (tune2fs -U ...).
>
> Your code looks like you copy the bytes to the in-kernel superblock
> structure without noticing any later changes on disk? How is that
> supposed to work?
I thought tune2fs on a mounted filesystem was always a
"you get to keep both pieces if it breaks" situation.
Dave
--
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