linux-kernel - Re: [PATCH] loop: add some basic read-only sysfs attributes

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: <4C5191A3.9070303@redhat.com>
Date:	Thu, 29 Jul 2010 16:35:15 +0200
From:	Milan Broz <mbroz@...hat.com>
To:	Kay Sievers <kay.sievers@...y.org>
CC:	util-linux-ng@...r.kernel.org, linux-kernel@...r.kernel.org,
	kzak@...hat.com, axboe@...nel.dk
Subject: Re: [PATCH] loop: add some basic read-only sysfs attributes

On 07/29/2010 04:22 PM, Kay Sievers wrote:
>> First 8 loop devices are registered always (without backing file),
>> so you have wait for change event initiated from fd set ioctl anyway...
>> (backing file attribute is empty in that case)
> 
> Ah, so we are sure, we always get a 'change' event, and before that,
> none of these values are ever useful to read? I mean, there will not
> be attributes that are interesting during an 'add' event?

I think it was already that way for all loop block devices...

See loop block devices registered during module init
(up to max_loop - which is 8 by default) and later configured by losetup.

Milan
--
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/