linux-kernel - Re: [PATCH 1/3] mtd: spi-nor: Export SFDP access to sysfs

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: <5e23722b1c7d6716c404667a3c5bfbff@walle.cc>
Date:   Wed, 28 Apr 2021 17:51:01 +0200
From:   Michael Walle <michael@...le.cc>
To:     Alexander Williams <awill@...gle.com>
Cc:     Miquel Raynal <miquel.raynal@...tlin.com>,
        Richard Weinberger <richard@....at>,
        Vignesh Raghavendra <vigneshr@...com>,
        Tudor Ambarus <tudor.ambarus@...rochip.com>,
        Pratyush Yadav <p.yadav@...com>, linux-mtd@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] mtd: spi-nor: Export SFDP access to sysfs

Am 2021-04-28 17:37, schrieb Alexander Williams:
> On Wed, Apr 28, 2021 at 12:58 AM Michael Walle <michael@...le.cc> 
> wrote:
>> 
>> Hi Alexander,
>> 
>> Am 2021-04-28 07:27, schrieb Alexander Williams:
>> > Add the ability to specify a technology-specific attribute_group, and
>> > expose the SFDP through spi-nor's private group. This enables user
>> > space
>> > to have full access to the contents of the SFDP, so all information is
>> > available without regard for whether the kernel supports parsing it.
>> 
>> Please see:
>> https://lore.kernel.org/linux-mtd/20210318092406.5340-1-michael@walle.cc/
> 
> Thanks for the pointer! Sorry I didn't see that patch series already: 
> My search
> skills need some work... In any case, there's no good reason for me to 
> duplicate
> work.
> 
> I should probably comment on that series directly, but I'll note that 
> one thing
> I tried to do with the sysfs attributes here was avoid racing with user 
> space.
> The uevent is suppressed until all the related files are created in 
> sysfs. See
> http://kroah.com/log/blog/2013/06/26/how-to-create-a-sysfs-file-correctly/ 
> for
> Greg's explanation of a scenario.

Sure, reviews and remarks are always welcome. Btw. what is patch 2/3 and 
3/3?
I couldn't find it on the LKML.

-michael