[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200705202009.39291.arvidjaar@mail.ru>
Date: Sun, 20 May 2007 20:09:38 +0400
From: Andrey Borzenkov <arvidjaar@...l.ru>
To: "Ray Lee" <ray-lk@...rabbit.org>
Cc: "Al Viro" <viro@....linux.org.uk>, "Uwe Bugla" <uwe.bugla@....de>,
"Ken Chen" <kenchen@...gle.com>, linux-kernel@...r.kernel.org,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Michal Piotrowski" <michal.k.k.piotrowski@...il.com>
Subject: Re: bug in 2.6.22-rc2: loop mount limited to one single iso image
On Sunday 20 May 2007, Ray Lee wrote:
> On 5/19/07, Al Viro <viro@....linux.org.uk> wrote:
> > On Sat, May 19, 2007 at 11:16:59PM -0700, Ray Lee wrote:
> > > Ken? Ball's in your court. As the patch isn't providing a killer
> > > feature for 2.6.22, I'd suggest just reverting it for now until the
> > > issues are ironed out.
> >
> > Hold it. The real question here is which logics do we want there.
> > IOW, and how many device nodes do we want to appear and _when_ do
> > we want them to appear?
>
> The when part is what looks to make it racy. I'm guessing that we're
> relying on udev to create those loop nodes. If so, I think any scheme
> that creates more on demand would give transient mount errors while
> it's waiting on udev to create more nodes.
>
this seems to work with /dev/pts though. May be, by accident?
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists