From: Ingo Molnar <mingo@kernel.org>
To: David Hildenbrand <david@redhat.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
kernel test robot <lkp@intel.com>,
oe-kbuild@lists.linux.dev, Dan Carpenter <error27@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
x86@kernel.org
Subject: Re: [PATCH v3] x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()
Date: Sun, 6 Apr 2025 19:17:34 +0200 [thread overview]
Message-ID: <Z_K3LkhQH05fP1T9@gmail.com> (raw)
In-Reply-To: <18abdf06-9d45-42bf-b666-af1a416bf2a6@redhat.com>
* David Hildenbrand <david@redhat.com> wrote:
> On 04.04.25 14:20, David Hildenbrand wrote:
> > On 04.04.25 13:52, Lorenzo Stoakes wrote:
> > > On Thu, Apr 03, 2025 at 10:59:12PM +0200, David Hildenbrand wrote:
> > > > On 03.04.25 17:14, Dan Carpenter wrote:
> > > > > Sorry, I've been having trouble with my email recently... I replied
> > > > > earlier but my email got eaten on the way out.
> > > > >
> > > > > What happened here is that the zero day bot emails go to me first and
> > > > > then I review them or forward them depending on if they're a real
> > > > > issue or not.
> > > > >
> > > > > Here it's a false postive because it's set and used if the
> > > > > (src_vma->vm_flags & VM_PFNMAP) flag is set. Smatch doesn't parse
> > > > > this correctly. I've been meaning to fix this in Smatch for a
> > > > > while.
> > > >
> > > > There is a slight complication (on top of the VM_PFNMAP checks):
> > > >
> > > > If "src_vma->vm_flags & VM_PAT" we
> > > > * set pfn
> > > > * set dst_vma->vm_flags |= VM_PFNMAP
> > > >
> > > > Then, we only consume the pfn if "dst_vma->vm_flags & VM_PFNMAP"
> > > >
> > > > While we won't be using the uninitialized pfn (good), we'd still pass an
> > > > uninitialized pfn, which IIRC is UB; likely nothing happens on GCC clang,
> > > > but we better handle it.
> > > >
> > > > So that should better be changed; I'll send a fix.
> > >
> > > Maybe just worth setting pfn = 0 _as well_ in the caller, belts + braces maybe?
> >
> > I'm planning on doing the following, just didn't get to testing it:
> >
>
> Ah, now I get your comment. Yeah, we could just set pfn=0 in the caller as
> well to make smatch completely happy I guess.
Yeah, that's far cleaner than these rather ugly code constructs in the
error paths. It's a pretty standard API where output pointers may not
get touched on errors - if Smatch has a problem with it, fix Smatch or
the callers.
Thanks,
Ingo
next prev parent reply other threads:[~2025-04-06 17:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 11:37 Lorenzo Stoakes
2025-04-03 15:14 ` [PATCH v3] x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() Dan Carpenter
2025-04-03 20:59 ` David Hildenbrand
2025-04-04 11:52 ` Lorenzo Stoakes
2025-04-04 12:20 ` David Hildenbrand
2025-04-04 12:27 ` David Hildenbrand
2025-04-06 17:17 ` Ingo Molnar [this message]
2025-04-07 7:11 ` Dan Carpenter
[not found] <202503270941.IFILyNCX-lkp@intel.com>
[not found] ` <9b3b3296-ab21-418b-a0ff-8f5248f9b4ec@lucifer.local>
[not found] ` <b21bcd61-faf0-4ad8-b644-99794794594f@redhat.com>
2025-04-02 11:40 ` Lorenzo Stoakes
-- strict thread matches above, loose matches on Subject: below --
2025-03-25 19:19 David Hildenbrand
2025-04-02 11:36 ` David Hildenbrand
2025-04-02 12:32 ` Lorenzo Stoakes
2025-04-03 14:47 ` David Hildenbrand
2025-04-03 14:50 ` Lorenzo Stoakes
2025-04-02 11:59 ` Lorenzo Stoakes
2025-04-02 12:20 ` David Hildenbrand
2025-04-02 12:31 ` Lorenzo Stoakes
2025-04-02 15:19 ` David Hildenbrand
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=Z_K3LkhQH05fP1T9@gmail.com \
--to=mingo@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=dan.carpenter@linaro.org \
--cc=david@redhat.com \
--cc=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=oe-kbuild@lists.linux.dev \
--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