From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] sysctl: introduce uuid_le and uuid_be
Date: Tue, 24 May 2016 23:25:30 +0300 [thread overview]
Message-ID: <1464121530.31269.86.camel@linux.intel.com> (raw)
In-Reply-To: <20160524131508.7277546c9620a0ad080f1e19@linux-foundation.org>
On Tue, 2016-05-24 at 13:15 -0700, Andrew Morton wrote:
> On Tue, 24 May 2016 20:27:27 +0300 Andy Shevchenko <andriy.shevchenko@
> linux.intel.com> wrote:
>
> > By default the sysctl interface returns random UUID in big endian
> > format.
> > Sometimes it's not suitable, e.g. using generated UUID for EFI
> > variable name.
> > Provide uuid_le and uuid_be to comprehence that interface.
> >
> > ...
> >
> > drivers/char/random.c | 44
> > +++++++++++++++++++++++++++++++++++++++++
> > include/uapi/linux/sysctl.h | 4 +++-
> > kernel/sysctl_binary.c | 48
> > ++++++++++++++++++++++++++++++++++++++++++++
>
> Why does the kernel need to do this? If userspace wants a random uuid
> then it can grab a random number and cook up the UUID itself.
Good question. I dunno why we have uuid in the first place there. At
some point I noticed people who recommend to use that file to get a
random UUID(s), but apparently they don't aware that endianess matters.
P.S. I thought to send this as RFC, but decided to drop the notation in
last minute. So, it's okay to drop it.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2016-05-24 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 17:27 [PATCH v1 1/1] sysctl: introduce uuid_le and uuid_be Andy Shevchenko
2016-05-24 20:15 ` Andrew Morton
2016-05-24 20:25 ` Andy Shevchenko [this message]
2016-05-24 22:56 ` Theodore Ts'o
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=1464121530.31269.86.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.