From: Al Viro <viro@zeniv.linux.org.uk>
To: Pascal Bouchareine <kalou@tfz.net>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-api@vger.kernel.org, Alexey Dobriyan <adobriyan@gmail.com>,
Jeff Layton <jlayton@poochiereds.net>,
"J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: [PATCH] proc,fcntl: introduce F_SET_DESCRIPTION
Date: Sat, 25 Jul 2020 23:10:22 +0100 [thread overview]
Message-ID: <20200725221022.GQ2786714@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20200725004043.32326-1-kalou@tfz.net>
On Fri, Jul 24, 2020 at 05:40:43PM -0700, Pascal Bouchareine wrote:
> This command attaches a description to a file descriptor for
> troubleshooting purposes. The free string is displayed in the
> process fdinfo file for that fd /proc/pid/fdinfo/fd.
>
> One intended usage is to allow processes to self-document sockets
> for netstat and friends to report
Have you even tried to test it? When will it ever free those things?
next prev parent reply other threads:[~2020-07-25 22:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 0:40 [PATCH] proc,fcntl: introduce F_SET_DESCRIPTION Pascal Bouchareine
2020-07-25 4:59 ` [PATCH v2] " Pascal Bouchareine
2020-07-25 5:15 ` [PATCH v3] This command attaches a description to a file descriptor for troubleshooting purposes. The free string is displayed in the process fdinfo file for that fd /proc/pid/fdinfo/fd Pascal Bouchareine
2020-07-26 2:11 ` Pascal Bouchareine
2020-07-25 5:22 ` [PATCH v3] proc,fcntl: introduce F_SET_DESCRIPTION Pascal Bouchareine
2020-07-27 14:21 ` Alexey Dobriyan
2020-07-28 1:39 ` Pascal Bouchareine
2020-07-28 6:25 ` Pascal Bouchareine
2020-07-25 22:10 ` Al Viro [this message]
2020-07-26 1:42 ` [PATCH] " Pascal Bouchareine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200725221022.GQ2786714@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=adobriyan@gmail.com \
--cc=bfields@fieldses.org \
--cc=jlayton@poochiereds.net \
--cc=kalou@tfz.net \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.