From: Oscar Salvador <osalvador@suse.de>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Peter Xu <peterx@redhat.com>, Muchun Song <muchun.song@linux.dev>,
David Hildenbrand <david@redhat.com>,
Donet Tom <donettom@linux.ibm.com>,
Matthew Wilcox <willy@infradead.org>,
Vlastimil Babka <vbabka@suse.cz>, Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH v2 6/9] mm: Make hugetlb mappings go through mm_get_unmapped_area_vmflags
Date: Thu, 1 Aug 2024 10:14:26 +0200 [thread overview]
Message-ID: <ZqtD4idp0IyHgSp5@localhost.localdomain> (raw)
In-Reply-To: <47de87e4-47df-4024-a313-03cc14b8e248@lucifer.local>
On Wed, Jul 31, 2024 at 05:15:41PM +0100, Lorenzo Stoakes wrote:
> I've not got the vm debug on in my build, so it's blowing up here for me:
>
> static unsigned long shm_get_unmapped_area(struct file *file,
> unsigned long addr, unsigned long len, unsigned long pgoff,
> unsigned long flags)
> {
> struct shm_file_data *sfd = shm_file_data(file);
>
> return sfd->file->f_op->get_unmapped_area(sfd->file, addr, len,
> pgoff, flags);
> }
>
> Notice that that doesn't check whether sfd->file->f_op->get_unmapped_area
> is NULL.
I see now, thanks.
> So since you remove this from the f_ops, it causes a NULL pointer deref.
...
> static const struct file_operations shm_file_operations = {
> ..
> .get_unmapped_area = shm_get_unmapped_area,
> ...
> };
>
> Then this get_area() is invoked, which calls shm_get_unmapped_area(), which
> calls f_op->get_unmapped_area() on your hugetlbfs_file_operations object
> which you just deleted and it's NULL.
>
> This is why you have to be super careful here, there's clearly stuff out
> there that assumes that this can't happen, which you need to track down.
>
> A quick grep however _suggests_ this might be the one landmine place. But
> you need to find a smart way to deal with this.
Probably, the most straightforward way to fix this is to instead of
setting .get_unmapped_area to NULL for hugetlbfs_file_operations, would
be to have it re-defined like:
.get_unmapped_area = mm_get_unmapped_area_vmflags
Which is what we call after this patchset.
So no more things have to tweaked.
On a more correct way, __maybe__ have something like:
diff --git a/ipc/shm.c b/ipc/shm.c
index 3e3071252dac..222dca8a3716 100644
--- a/ipc/shm.c
+++ b/ipc/shm.c
@@ -648,8 +648,11 @@ static unsigned long shm_get_unmapped_area(struct file *file,
{
struct shm_file_data *sfd = shm_file_data(file);
- return sfd->file->f_op->get_unmapped_area(sfd->file, addr, len,
+ if (sfd->file->f_op->get_unmapped_area)
+ return sfd->file->f_op->get_unmapped_area(sfd->file, addr, len,
pgoff, flags);
+
+ return mm_get_unmapped_area_vmflags(sfd->file, addr, len, pgoff, flags);
}
static const struct file_operations shm_file_operations = {
Still unsure about which approach looks more correct though.
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2024-08-01 8:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 9:10 [PATCH v2 0/9] Unify hugetlb into arch_get_unmapped_area functions Oscar Salvador
2024-07-29 9:10 ` [PATCH v2 1/9] mm/mmap: Teach generic_get_unmapped_area{_topdown} to handle hugetlb mappings Oscar Salvador
2024-07-29 9:10 ` [PATCH v2 2/9] arch/s390: Teach arch_get_unmapped_area{_topdown} " Oscar Salvador
2024-07-29 9:10 ` [PATCH v2 3/9] arch/x86: Teach arch_get_unmapped_area_vmflags " Oscar Salvador
2024-07-29 9:10 ` [PATCH v2 4/9] arch/sparc: Teach arch_get_unmapped_area{_topdown} " Oscar Salvador
2024-07-29 9:10 ` [PATCH v2 5/9] arch/powerpc: Teach book3s64 " Oscar Salvador
2024-07-29 9:10 ` [PATCH v2 6/9] mm: Make hugetlb mappings go through mm_get_unmapped_area_vmflags Oscar Salvador
2024-07-31 11:02 ` Lorenzo Stoakes
2024-07-31 15:08 ` Oscar Salvador
2024-07-31 15:11 ` Oscar Salvador
2024-07-31 20:03 ` Andrew Morton
2024-07-31 15:19 ` Lorenzo Stoakes
2024-07-31 16:04 ` Oscar Salvador
2024-07-31 16:15 ` Lorenzo Stoakes
2024-08-01 8:14 ` Oscar Salvador [this message]
2024-08-01 10:11 ` Lorenzo Stoakes
2024-08-05 21:03 ` kernel test robot
2024-08-11 13:23 ` kernel test robot
2024-07-29 9:10 ` [PATCH v2 7/9] mm: Drop hugetlb_get_unmapped_area{_*} functions Oscar Salvador
2024-07-29 9:10 ` [PATCH v2 8/9] arch/s390: Clean up hugetlb definitions Oscar Salvador
2024-07-29 9:10 ` [PATCH v2 9/9] mm: Consolidate common checks in hugetlb_mmap_check_and_align Oscar Salvador
2024-07-30 9:59 ` kernel test robot
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=ZqtD4idp0IyHgSp5@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=donettom@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=peterx@redhat.com \
--cc=vbabka@suse.cz \
--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