linux-kernel - Re: [patch 01/26] mount options: add documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <E1JKdR1-00030N-3x@pomaz-ex.szeredi.hu>
Date:	Thu, 31 Jan 2008 18:42:47 +0100
From:	Miklos Szeredi <miklos@...redi.hu>
To:	kzak@...hat.com
CC:	miklos@...redi.hu, zippel@...ux-m68k.org,
	akpm@...ux-foundation.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, sfrench@...ibm.com, lachlan@....com,
	jsipek@...sunysb.edu, rmk@....linux.org.uk, dhowells@...hat.com,
	raven@...maw.net, rathamahata@...4.ru, kkeil@...e.de,
	hpa@...or.com, tytso@....edu, hirofumi@...l.parknet.co.jp,
	jdike@...toit.com, mikulas@...ax.karlin.mff.cuni.cz,
	wli@...omorphy.com, shaggy@...tin.ibm.com, vandrove@...cvut.cz,
	Trond.Myklebust@...app.com, jeffm@...e.com, paulus@...ba.org,
	hugh@...itas.com, gorcunov@...il.com, gregkh@...e.de
Subject: Re: [patch 01/26] mount options: add documentation

> > > - loop: how is the connection between file and loop device maintained?
> > 
> > We also discussed this with Karel, maybe it didn't make it onto lkml.
> > 
> > The proposed solution was to store the "loop" flag separately in a
> > file under /var.  It could just be an empty file for each such loop
> > device:
> > 
> >   /var/lib/mount/loops/loop0
> > 
> > This file is created by mount(8) if the '-oloop' option is given.  And
> > umount(8) automatically tears down the loop device if it finds this
> > file.
> 
>  It seems we needn't this solution. There is loop auto-destruction
>  patch in -mm.
> 
>  Kernel part:
>     http://marc.info/?l=linux-kernel&m=119361296818388&w=2
> 
>  mount(8) part:
>     http://marc.info/?l=util-linux-ng&m=119362955431694&w=2
> 
>  So, with this patch mount(8) needn't to maintain info about loops and
>  umount(8) doesn't need to call LOOP_CLR_FD ioctl, because umount(2)
>  is enough.

Excellent!  This is a very good example how moving a functionality
into the kernel can greatly simplify it.

Thanks,
Miklos
--
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/