From: Matthew Wilcox <willy@infradead.org>
To: "José Pekkarinen" <jose.pekkarinen@foxhound.fi>
Cc: akpm@linux-foundation.org, skhan@linuxfoundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev,
syzbot+89edd67979b52675ddec@syzkaller.appspotmail.com,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH] mm/pgtable: return null if no ptl in __pte_offset_map_lock
Date: Wed, 15 Nov 2023 14:19:26 +0000 [thread overview]
Message-ID: <ZVTTbuviH9/RWYyI@casper.infradead.org> (raw)
In-Reply-To: <20231115065506.19780-1-jose.pekkarinen@foxhound.fi>
On Wed, Nov 15, 2023 at 08:55:05AM +0200, José Pekkarinen wrote:
> Documentation of __pte_offset_map_lock suggest there is situations where
You should have cc'd Hugh who changed all this code recently.
> a pmd may not have a corresponding page table, in which case it should
> return NULL without changing ptlp. Syzbot found its ways to produce a
> NULL dereference in the function showing this case. This patch will
> provide the exit path suggested if this unlikely situation turns up. The
> output of the kasan null-ptr-report follows:
There's no need to include all this nonsense in the changelog.
> spin_lock include/linux/spinlock.h:351 [inline]
> __pte_offset_map_lock+0x154/0x360 mm/pgtable-generic.c:373
> pte_offset_map_lock include/linux/mm.h:2939 [inline]
> filemap_map_pages+0x698/0x11f0 mm/filemap.c:3582
This was the only interesting part.
> +++ b/include/linux/mm.h
> @@ -2854,7 +2854,7 @@ void ptlock_free(struct ptdesc *ptdesc);
>
> static inline spinlock_t *ptlock_ptr(struct ptdesc *ptdesc)
> {
> - return ptdesc->ptl;
> + return (likely(ptdesc)) ? ptdesc->ptl : NULL;
> }
I don't think we should be changing ptlock_ptr().
> +++ b/mm/pgtable-generic.c
> @@ -370,6 +370,8 @@ pte_t *__pte_offset_map_lock(struct mm_struct *mm, pmd_t *pmd,
> if (unlikely(!pte))
> return pte;
> ptl = pte_lockptr(mm, &pmdval);
> + if (unlikely(!ptl))
> + return NULL;
> spin_lock(ptl);
I don't understand how this could possibly solve the problem. If there's
no PTE level, then __pte_offset_map() should return NULL and we'd already
return due to the check for !pte.
next prev parent reply other threads:[~2023-11-15 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 6:55 José Pekkarinen
2023-11-15 14:19 ` Matthew Wilcox [this message]
2023-11-15 16:05 ` José Pekkarinen
2023-11-15 19:04 ` Matthew Wilcox
2023-11-16 7:23 ` Hugh Dickins
2023-11-16 8:26 ` Hugh Dickins
2023-11-16 10:04 ` José Pekkarinen
2023-11-17 6:13 ` Hugh Dickins
2023-11-17 9:16 ` José Pekkarinen
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=ZVTTbuviH9/RWYyI@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=jose.pekkarinen@foxhound.fi \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+89edd67979b52675ddec@syzkaller.appspotmail.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