linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Karel Zak <kzak@redhat.com>, Masatake YAMATO <yamato@redhat.com>,
	linux-api@vger.kernel.org
Subject: Re: [PATCH] proc: add byteorder file
Date: Tue, 1 Nov 2022 05:42:36 +0100	[thread overview]
Message-ID: <cb411513-9cb0-482f-8642-43704c2bfa52@t-8ch.de> (raw)
In-Reply-To: <Y2Chv8uO04ahV9W8@kroah.com>

On 2022-11-01 05:34+0100, Greg KH wrote:
> On Tue, Nov 01, 2022 at 01:50:43AM +0100, Thomas Weißschuh wrote:
> > Certain files in procfs are formatted in byteorder dependent ways. For
> > example the IP addresses in /proc/net/udp.
> > 
> > Assuming the byteorder of the userspace program is not guaranteed to be
> > correct in the face of emulation as for example with qemu-user.
> > 
> > Also this makes it easier for non-compiled applications like
> > shellscripts to discover the byteorder.
> > 
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> 
> Why not put this in /sys/kernel/ instead?  What does this have to do
> with /proc/ other than it's traditionally been the dumping ground for
> stuff like this?  :)

The main reason to put it in /proc was because the data it helps to interpret
is also in /proc.

But /sys/kernel looks good, too. I'll change it to that.

      reply	other threads:[~2022-11-01  4:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  0:50 [PATCH] proc: add byteorder file Thomas Weißschuh
2022-11-01  4:34 ` Greg KH
2022-11-01  4:42   ` Thomas Weißschuh [this message]

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=cb411513-9cb0-482f-8642-43704c2bfa52@t-8ch.de \
    --to=linux@weissschuh.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=kzak@redhat.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yamato@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).