From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Fei Li <fei1.li@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH v4 1/1] virt: acrn: Mark the uuid field as unused
Date: Wed, 16 Nov 2022 15:29:31 +0200 [thread overview]
Message-ID: <Y3Tlu0BjgMk3xNDQ@smile.fi.intel.com> (raw)
In-Reply-To: <Y3TMmDXEbGyDQrLF@kroah.com>
On Wed, Nov 16, 2022 at 12:42:16PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Nov 16, 2022 at 11:22:54AM +0200, Andy Shevchenko wrote:
> > After the commits for userspace (see Link tags below) the uuid field is
> > not being used in the ACRN code. Update kernel to reflect these changes.
> > I.e. we do the following:
> > - adding a comment explaining that it's not used anymore
> > - replacing the specific type by a raw buffer
> > - updating the example code accordingly
> >
> > The advertised field confused users and actually never been used. So
> > the wrong part here is that kernel puts something which userspace never
> > used and hence this may confuse a reader of this code.
> > - * @uuid: UUID of the VM. Pass to hypervisor directly.
> > + * @uuid: Reserved (used to be UUID of the VM)
>
> If it's reserved, then don't you need to check for 0?
Reserved in a way that it may content something we just don't care about.
...
> > + __u8 uuid[16];
>
> You just changed the type here, so what is that going to break in
> userspace that depended on this being of a structure type and now it's
> an array?
It's the same. The previous was hidden behind additional type level.
> And no other kernel changes needed? Shouldn't you warn if this field is
> set?
No, as pointed out in the commit message kernel never ever used this.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-11-16 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 9:22 [PATCH v4 1/1] virt: acrn: Mark the uuid field as unused Andy Shevchenko
2022-11-16 11:42 ` Greg Kroah-Hartman
2022-11-16 13:29 ` Andy Shevchenko [this message]
2022-11-16 15:20 ` Greg Kroah-Hartman
2022-11-16 16:04 ` Andy Shevchenko
2022-11-16 16:16 ` Greg Kroah-Hartman
2022-11-16 16:31 ` Andy Shevchenko
2022-11-17 1:03 ` Fei Li
2022-11-17 6:47 ` Andy Shevchenko
2022-11-17 6:50 ` Andy Shevchenko
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=Y3Tlu0BjgMk3xNDQ@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=fei1.li@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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.