From: Andrew Morton <akpm@linux-foundation.org>
To: Yang Shi <yang@os.amperecomputing.com>
Cc: muchun.song@linux.dev, catalin.marinas@arm.com, will@kernel.org,
linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hugetlbfs: add MTE support
Date: Wed, 26 Jun 2024 13:40:40 -0700 [thread overview]
Message-ID: <20240626134040.63fe621bff6a5fe1c0503999@linux-foundation.org> (raw)
In-Reply-To: <20240625233717.2769975-1-yang@os.amperecomputing.com>
On Tue, 25 Jun 2024 16:37:17 -0700 Yang Shi <yang@os.amperecomputing.com> wrote:
> MTE can be supported on ram based filesystem. It is supported on tmpfs.
> There is use case to use MTE on hugetlbfs as well, adding MTE support.
>
> --- a/fs/hugetlbfs/inode.c
> +++ b/fs/hugetlbfs/inode.c
> @@ -110,7 +110,7 @@ static int hugetlbfs_file_mmap(struct file *file, struct vm_area_struct *vma)
> * way when do_mmap unwinds (may be important on powerpc
> * and ia64).
> */
> - vm_flags_set(vma, VM_HUGETLB | VM_DONTEXPAND);
> + vm_flags_set(vma, VM_HUGETLB | VM_DONTEXPAND | VM_MTE_ALLOWED);
> vma->vm_ops = &hugetlb_vm_ops;
>
> ret = seal_check_write(info->seals, vma);
How thoroughly has this been tested?
Can we expect normal linux-next testing to exercise this, or must
testers make special arangements to get the coverage?
next prev parent reply other threads:[~2024-06-26 20:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 23:37 Yang Shi
2024-06-26 20:40 ` Andrew Morton [this message]
2024-06-26 20:45 ` Yang Shi
2024-06-26 23:43 ` Yang Shi
2024-07-02 12:34 ` Catalin Marinas
2024-07-02 13:09 ` David Hildenbrand
2024-07-03 0:20 ` Yang Shi
2024-07-03 10:24 ` David Hildenbrand
2024-07-03 13:57 ` Catalin Marinas
2024-07-03 0:04 ` Yang Shi
2024-07-03 0:15 ` Yang Shi
2024-07-04 13:44 ` Catalin Marinas
2024-07-09 17:42 ` Yang Shi
2024-08-13 17:08 ` Yang Shi
2024-08-15 10:31 ` Catalin Marinas
2024-08-15 19:15 ` Yang Shi
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=20240626134040.63fe621bff6a5fe1c0503999@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=will@kernel.org \
--cc=yang@os.amperecomputing.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