[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240626134040.63fe621bff6a5fe1c0503999@linux-foundation.org>
Date: Wed, 26 Jun 2024 13:40:40 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Yang Shi <yang@...amperecomputing.com>
Cc: muchun.song@...ux.dev, catalin.marinas@....com, will@...nel.org,
linux-mm@...ck.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] hugetlbfs: add MTE support
On Tue, 25 Jun 2024 16:37:17 -0700 Yang Shi <yang@...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?
Powered by blists - more mailing lists