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] [day] [month] [year] [list]
Message-ID: <878qjvefj2.fsf@bootlin.com>
Date: Thu, 07 Aug 2025 09:50:57 +0200
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Gabor Juhos <j4g8y7@...il.com>
Cc: Richard Weinberger <richard@....at>,  Vignesh Raghavendra
 <vigneshr@...com>,  linux-kernel@...r.kernel.org,
  linux-mtd@...ts.infradead.org
Subject: Re: [PATCH] mtd: expose ooblayout information via sysfs

Hi Gabor,

>> I would prefer a debugfs entry, as this is mostly focusing on
>> development and debugging purposes. sysfs has a stable API, which makes
>> it a less relevant place in this case.
>
> Sorry, it seems that I misunderstood the ABI documentation.
>
> Since the 'sysfs-class-mtd' file is under the 'testing' directory
> within

It is indeed unclear. I'm not sure myself what that exactly means TBH,
but it's been there for a long time and can for sure be considered
stable. Sysfs in general is not for debugging.

> 'Documentation/ABI' I thought that it can be extended by attributes used for
> testing purposes. Additionally, the 'oobavail' and 'oobsize' attributes are
> exposed via sysfs, so it seemed to be a logical place for the new oob related ones.
>
> Nevertheless, I will check what can I do with the debugfs based
> approach.

Sure, thanks!

Miquèl

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ