[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGbU3_kOhXEx2s19P==F2-CyHFGbX_qKVWhPi+kPe3tmsY=HfA@mail.gmail.com>
Date: Thu, 13 Aug 2020 22:48:55 -0700
From: Pascal Bouchareine <kalou@....net>
To: Christoph Hellwig <hch@...radead.org>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-api@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Alexey Dobriyan <adobriyan@...il.com>,
Al Viro <viro@...iv.linux.org.uk>,
Jeff Layton <jlayton@...chiereds.net>,
"J. Bruce Fields" <bfields@...ldses.org>
Subject: Re: [PATCH v4 2/2] fcntl: introduce F_SET_DESCRIPTION
On Thu, Aug 13, 2020 at 10:28 PM Christoph Hellwig <hch@...radead.org> 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