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  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]
Date:   Thu, 13 Aug 2020 22:48:55 -0700
From:   Pascal Bouchareine <>
To:     Christoph Hellwig <>
        Andrew Morton <>,
        Alexey Dobriyan <>,
        Al Viro <>,
        Jeff Layton <>,
        "J. Bruce Fields" <>
Subject: Re: [PATCH v4 2/2] fcntl: introduce F_SET_DESCRIPTION

On Thu, Aug 13, 2020 at 10:28 PM Christoph Hellwig <> wrote:
> > One intended usage is to allow processes to self-document sockets
> > for netstat and friends to report
> NAK.  There is no way we're going to bloat a criticial structure like
> struct file for some vanity information like this.

The useful case is for sockets - Is there a more suited place to do that?
Do you think adding a setsockopt and sk_description to struct sock
would work, or would be considered the same?

Powered by blists - more mailing lists