loop problems continue in 2.4.3
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 3 lines · Jeff Garzik
Can you try 2.4.4-pre3?
ftp://ftp.us.kernel.org/pub/linux/kernel/testing/
I am testing loop behaviour in 2.4.3 and 3.4.4p3. I have noticed something disturbing:
I can mount the same file on the same mountpoint more than once. If I mount a file twice (same file on the same mount point)
both mounts (identical) show when I do df or cat /proc/mounts. If I issue unmount (once), both mounts disappear from df output, but one of them remains in /proc/mounts. If I issue umount again, the second mount disappers from cat /proc/mounts output, but the module 'loop' shows as busy and cannot be removed even though there are no more loop mounts. lsmod shows loop being used by 1 process.
If I repeat this whole procedure again, loop will be used by 2 processess in the end. I guess something is wrong here.
This experiment has been done under 2.4.4pre3. I will try the same under 2.4.3.
cheers,
Arthur
Quoted 5 lines · Arthur Pedyczak
Quoted 3 lines · Jeff Garzik
Can you try 2.4.4-pre3?
ftp://ftp.us.kernel.org/pub/linux/kernel/testing/
...the same thing happens in 2.4.3...
Quoted 25 lines
I am testing loop behaviour in 2.4.3 and 3.4.4p3. I have noticed something disturbing:
I can mount the same file on the same mountpoint more than once. If I mount a file twice (same file on the same mount point)
both mounts (identical) show when I do df or cat/proc/mounts. If I issue unmount (once), both mounts disappear from df output, but one of them remains in/proc/mounts. If I issue umount again, the second mount disappers from cat/proc/mountsoutput, but the module 'loop' shows as busy and cannot be removed even though there are no more loop mounts. lsmod shows loop being used by 1 process.
If I repeat this whole procedure again, loop will be used by 2 processess in the end. I guess something is wrong here.
This experiment has been done under 2.4.4pre3. I will try the same under 2.4.3.cheers,
Arthur-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 10 lines · Arthur Pedyczak
Quoted 3 lines · Jeff Garzik
Can you try 2.4.4-pre3?
ftp://ftp.us.kernel.org/pub/linux/kernel/testing/I am testing loop behaviour in 2.4.3 and 3.4.4p3. I have noticed something disturbing:
I can mount the same file on the same mountpoint more than once. If I mount a file twice (same file on the same mount point)
This is a 2.4 feature
Signature · 1 line
Jens Axboe
Quoted 4 lines · Jens Axboe
Quoted 2 lines
I can mount the same file on the same mountpoint more than once. If I mount a file twice (same file on the same mount point)
This is a 2.4 feature
Ability to losetup different loop devices to the same underlying file is a bug, though. Not that it was new, though...
Quoted 11 lines · Alexander Viro
Quoted 4 lines · Jens Axboe
Quoted 2 lines
I can mount the same file on the same mountpoint more than once. If I mount a file twice (same file on the same mount point)
This is a 2.4 feature
Ability to losetup different loop devices to the same underlying file is a bug, though. Not that it was new, though...
But the guy said:
"
Quoted 2 lines
disappers from cat
/proc/mountsoutput, but the module 'loop' shows as busy and cannot be removed even though there are no more loop mounts.
"
So he has no loop mounts and he can not remove the module. This is a bug!
Signature · 3 lines
Mircea Damian E-mails: [email protected], [email protected] WebPage: http://taz.mania.k.ro/~dmircea/
Quoted 11 lines · Alexander Viro
Quoted 4 lines · Jens Axboe
Quoted 2 lines
I can mount the same file on the same mountpoint more than once. If I mount a file twice (same file on the same mount point)
This is a 2.4 feature
Ability to losetup different loop devices to the same underlying file is a bug, though. Not that it was new, though...
It's also so close to 'doctor it hurts' that I don't think that's a big deal. Besides, if we later on want to have size limitited loop on files (some have already expressed wishes in this direction), we'll do this anyway.
Signature · 1 line
Jens Axboe
Quoted 7 lines · Mircea Damian
But the guy said:
"Quoted 2 lines
disappers from cat
/proc/mountsoutput, but the module 'loop' shows as busy and cannot be removed even though there are no more loop mounts."
So he has no loop mounts and he can not remove the module. This is a bug!
Ah indeed, I'll take a look.
Signature · 1 line
Jens Axboe