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: <4C518AC9.4040208@redhat.com>
Date:	Thu, 29 Jul 2010 16:06:01 +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 03:47 PM, Kay Sievers wrote:
> On Thu, Jul 29, 2010 at 15:33, Milan Broz <mbroz@...hat.com> wrote:
>> Create /sys/block/loopX/loop directory and provide these attributes:
>>  - backing_file
>>  - autoclear
>>  - offset
>>  - sizelimit
>>
>> To be used in util-linux-ng (and possibly elsewhere like udev rules)
>> where code need to get loop attributes from kernel (and not store
>> duplicate info in userspace).
> 
> Isn't it that the loop attributes are created _after_ the loopdev is
> registered? That would make it hard to use these attributes from udev,
> as the event is already running while they are created.

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)

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/