linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: TwT pupupu <tianwentong2000@gmail.com>
To: "Huang, Kai" <kai.huang@intel.com>
Cc: "jarkko@kernel.org" <jarkko@kernel.org>,
	 "dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	 "linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	 "mingo@redhat.com" <mingo@redhat.com>,
	"tglx@kernel.org" <tglx@kernel.org>,
	 "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"bp@alien8.de" <bp@alien8.de>,  "x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH] x86/sgx: use vm_flags_t for vm_prot_bits
Date: Fri, 23 Jan 2026 14:15:49 +0800	[thread overview]
Message-ID: <CAGPELS5G42Esir0LHz6gAHKsO5gas48XiMtfOeQ+Kn62rDuicg@mail.gmail.com> (raw)
In-Reply-To: <bfaa49c58626932e65096b433c7f37a2c35ca382.camel@intel.com>

On Wed, Jan 22, 2026 at 7:42 PM Huang, Kai <kai.huang@intel.com> wrote:
> Not sure we should change that too:
>
> struct sgx_encl_page {
> unsigned long desc;
> vm_flags_t vm_max_prot_bits:8;
> ...
> };
>
> ?
Hi, I'll include this in v2 for consistency. The :8
width is unchanged, so no functional or storage difference.

Huang, Kai <kai.huang@intel.com> 於 2026年1月22日週四 下午7:42寫道:
>
> On Thu, 2026-01-22 at 13:54 +0800, Wentong Tian wrote:
> > The vm_flags_t type is the dedicated type for virtual memory flags.
> > Architecture and driver code should use this type instead of assuming
> > vm_flags is an unsigned long, as the underlying type may change in the
> > future.
> >
> > This follows the cleanup in commit d75fa3c94750 ("mm: update
> > architecture and driver code to use vm_flags_t") by converting the
> > remaining vm_prot_bits usage in SGX code.
> >
> > No functional change intended.
> >
> > Signed-off-by: Wentong Tian <tianwentong2000@gmail.com>
> > ---
> >  arch/x86/kernel/cpu/sgx/encl.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/x86/kernel/cpu/sgx/encl.c b/arch/x86/kernel/cpu/sgx/encl.c
> > index cf149b9f4916..814edcde225d 100644
> > --- a/arch/x86/kernel/cpu/sgx/encl.c
> > +++ b/arch/x86/kernel/cpu/sgx/encl.c
> > @@ -281,7 +281,7 @@ static struct sgx_encl_page *sgx_encl_load_page_in_vma(struct sgx_encl *encl,
> >                                                      unsigned long addr,
> >                                                      vm_flags_t vm_flags)
> >  {
> > -     unsigned long vm_prot_bits = vm_flags & VM_ACCESS_FLAGS;
> > +     vm_flags_t vm_prot_bits = vm_flags & VM_ACCESS_FLAGS;
> >       struct sgx_encl_page *entry;
> >
> >       entry = xa_load(&encl->page_array, PFN_DOWN(addr));
>
> Since commit d75fa3c94750 ("mm: update
> architecture and driver code to use vm_flags_t") already converted one
> 'vm_prot_bits' to vm_flags_t in sgx_encl_may_map(), this looks good to me
> too.
>
> One thing though:
>
> 'vm_prot_bits' is later bit-ANDed with entry->vm_max_prot_bits:
>
>         if ((entry->vm_max_prot_bits & vm_prot_bits) != vm_prot_bits)
>                 return ERR_PTR(-EFAULT);
>
> But 'vm_max_prot_bits' a 8-bit field of 'unsigned long' in 'struct
> sgx_encl_page':
>
>         struct sgx_encl_page {
>                 unsigned long desc;
>                 unsigned long vm_max_prot_bits:8;
>                 ...
>         };
>
> Not sure we should change that too:
>
>         struct sgx_encl_page {
>                 unsigned long desc;
>                 vm_flags_t vm_max_prot_bits:8;
>                 ...
>         };
>
> ?


  reply	other threads:[~2026-01-23  6:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22  5:54 Wentong Tian
2026-01-22 11:42 ` Huang, Kai
2026-01-23  6:15   ` TwT pupupu [this message]
2026-01-25 14:45 ` Jarkko Sakkinen

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=CAGPELS5G42Esir0LHz6gAHKsO5gas48XiMtfOeQ+Kn62rDuicg@mail.gmail.com \
    --to=tianwentong2000@gmail.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=jarkko@kernel.org \
    --cc=kai.huang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-sgx@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@kernel.org \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox