From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v1] mei: Don't encourage to use kernel internal types in user code
Date: Mon, 2 Mar 2020 17:58:18 +0200 [thread overview]
Message-ID: <20200302155818.GG1224808@smile.fi.intel.com> (raw)
In-Reply-To: <3bb5abe91919458aa6166eb60d9451ff@intel.com>
+Cc: Christoph.
On Sat, Feb 29, 2020 at 04:28:11PM +0000, Winkler, Tomas wrote:
> > uuid_le is internal kernel type which shall not be exposed to the user in the first
> > place.
> Why, these types are exported via include/uapi/linux/uuid.h
Which is wrong from the day 1.
The uuid_t type is being provided by libuuid in the user space, there is no
(more) kernel exported equivalent. Same should be done to the uuid_le.
We already discussed this couple of years ago.
> In order to mitigate the (wrong) distribution of the use of that type,
> > switch MEI AMT sample to plain unsigned char array.
>
> There was a change to guid_t from uuild_le, anyhow there is much more code
> except this sample that uses those types.
I guess you misunderstood the point. The types are for kernel use and keeping them
exported in a condition like it's now (quoter baked due to drop of uuid_be part
completely and uuid_le partially) is wrong.
There is *no* ABI change. And basically libuuid or another one should provide
type and infrastructure for this.
> Nack so far.
If you would like to bear the legacy type, why not to move this UUID UAPI parts
directly to MEI?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-03-02 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 15:13 Andy Shevchenko
2020-02-29 16:28 ` Winkler, Tomas
2020-03-02 15:58 ` Andy Shevchenko [this message]
2020-03-02 18:05 ` Winkler, Tomas
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=20200302155818.GG1224808@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@intel.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
Powered by JetHome