netdev - Re: [PATCH RFC v1] rds: Expose feature parameters via sysfs and ELF note

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: <aEibdVJDL7oolbc1@char.us.oracle.com>
Date: Tue, 10 Jun 2025 16:54:13 -0400
From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: allison.henderson@...cle.com, netdev@...r.kernel.org,
        linux-rdma@...r.kernel.org, rds-devel@....oracle.com
Subject: Re: [PATCH RFC v1] rds: Expose feature parameters via sysfs and ELF
 note

On Tue, Jun 10, 2025 at 10:50:06PM +0200, Andrew Lunn wrote:
> > Right..
> > > as /dev/null.
> > 
> > Not sure I follow. Make them the same a /dev/null? Meaning link them to
> > /dev/null when the module is loaded?
> 
> I mean the contents of the file does not matter. All that matters is
> if the file exists or not. The IOCTL etc should never change, and if
> they do, the patch which changes them will be reverted. So i would
> make them a 0 byte file. You can even make it have mode 0000.

Gotcha! That seems to run counter to what the sysfs expects?

It has to have _something_ in them. But let me play around and see.

Thanks for the feedback!
> 
> However, i would first try to copy existing ideas...

Yup, lets see what the other folks have to say.
> 
> 	Andrew