On Sunday 20 May 2007, Ray Lee wrote: > On 5/19/07, Al Viro <[email protected]> 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?
Attachment:
pgpsZctljsa4S.pgp
Description: PGP signature
- Follow-Ups:
- References:
- Re: bug in 2.6.22-rc2: loop mount limited to one single iso image
- From: Ray Lee <[email protected]>
- Re: bug in 2.6.22-rc2: loop mount limited to one single iso image
- From: Al Viro <[email protected]>
- Re: bug in 2.6.22-rc2: loop mount limited to one single iso image
- From: "Ray Lee" <[email protected]>
- Re: bug in 2.6.22-rc2: loop mount limited to one single iso image
- Prev by Date: Re: bug in 2.6.22-rc2: loop mount limited to one single iso image
- Next by Date: Re: signals logged / [RFC] log out-of-virtual-memory events
- Previous by thread: Re: bug in 2.6.22-rc2: loop mount limited to one single iso image
- Next by thread: Re: bug in 2.6.22-rc2: loop mount limited to one single iso image
- Index(es):
 |