From: Andrew Morton <akpm@linux-foundation.org>
To: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
Cc: linux-kernel@vger.kernel.org, jgg@ziepe.ca,
Liam.Howlett@Oracle.com, jhubbard@nvidia.com, david@redhat.com,
willy@infradead.org,
linux-kernel-mentees@lists.linuxfoundation.org,
Suren Baghdasaryan <surenb@google.com>
Subject: Re: [RFC PATCH v1 1/1] linux: mm_types: allow to modified the vm_flags in vm_area_struct
Date: Sun, 12 Mar 2023 17:57:03 -0700 [thread overview]
Message-ID: <20230312175703.d8d8e0192387dfa9592ee8e5@linux-foundation.org> (raw)
In-Reply-To: <20230312224250.425727-1-vincenzopalazzodev@gmail.com>
On Sun, 12 Mar 2023 23:42:50 +0100 Vincenzo Palazzo <vincenzopalazzodev@gmail.com> wrote:
> With 6.3-rc1 is not possible to build the following drivers
Well, let's cc Suren who actually wrote bc292ab00f6c ("mm: introduce
vma->vm_flags wrapper functions").
> - nvidia, that the compilation returns the following errors
>
> - vboxhost/7.0.6_OSE where the build fails with the following errors
>
> ...
>
> --- a/include/linux/mm_types.h
> +++ b/include/linux/mm_types.h
> @@ -497,7 +497,7 @@ struct vm_area_struct {
> * To modify use vm_flags_{init|reset|set|clear|mod} functions.
> */
> union {
> - const vm_flags_t vm_flags;
> + vm_flags_t vm_flags;
> vm_flags_t __private __vm_flags;
> };
These out-of-tree drivers should be converted to use the wrappers which
bc292ab00f6c added. Their maintainers have a couple of months to do
this before bc292ab00f6c is released in 6.3.
It's unfortunate. I guess it would be better if we were to find a way
to permit these drivers to compile OK but to generate warnings, as an
interim thing for six months or so. Perhaps there's some clever way.
next prev parent reply other threads:[~2023-03-13 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 22:42 [RFC PATCH v1 1/1] linux: mm_types: allow to modified the vm_flags in vm_area_struct Vincenzo Palazzo
2023-03-13 0:57 ` Andrew Morton [this message]
2023-03-13 9:25 ` Vincenzo Palazzo
2023-03-13 9:50 ` Greg KH
2023-03-13 14:29 ` Suren Baghdasaryan
2023-03-13 6:34 ` Greg KH
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=20230312175703.d8d8e0192387dfa9592ee8e5@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@Oracle.com \
--cc=david@redhat.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=surenb@google.com \
--cc=vincenzopalazzodev@gmail.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox