linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: "Liam R. Howlett" <Liam.Howlett@Oracle.com>,
	kernel test robot <oliver.sang@intel.com>,
	oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>
Subject: Re: [linus:master] [mm/mmap] 04241ffe3f: Kernel_panic-not_syncing:Fatal_exception
Date: Wed, 1 Mar 2023 20:10:26 +0100	[thread overview]
Message-ID: <45eeb539-ed82-4984-197b-3f88cd765a59@suse.cz> (raw)
In-Reply-To: <20230301165036.mal6lkb6qhpjyz2r@revolver>

On 3/1/23 17:50, Liam R. Howlett wrote:
> * kernel test robot <oliver.sang@intel.com> [230301 02:21]:
>> 
>> Greeting,
>> 
>> FYI, we noticed Kernel_panic-not_syncing:Fatal_exception due to commit (built with gcc-11):
>> 
>> commit: 04241ffe3f0458d54c61cf6c9d58d703efda4dd5 ("mm/mmap: introduce dup_vma_anon() helper")
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>> 
>> [test failed on linus/master f3a2439f20d918930cc4ae8f76fe1c1afd26958f]
>> [test failed on linux-next/master 7f7a8831520f12a3cf894b0627641fad33971221]
> 
> I tracked the problem down in that commit.  The fix is simple enough:
> 
> -----------------
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -802,10 +802,13 @@ int __vma_adjust(struct vma_iterator *vmi, struct vm_area_struct *vma,
>                          * If next doesn't have anon_vma, import from vma after
>                          * next, if the vma overlaps with it.
>                          */
> -                       if (remove != NULL && !next->anon_vma)
> +                       if (remove2 != NULL && !next->anon_vma)

Oh I actually did notice that one too, but as it was only temporary within
the series and already baked into git, thought there's no benefit in
pointing it out. A problem for bisect obviously as was just confirmed.

> ----------------
> 
> However, that will not fix the problem in linux-next or linus/master
> since this code is completely changed shortly after.
> 
> You need the fix from Vlastimil (Cc'ed).  After cherry-picking

> 07dc4b186203 ("mm/mremap: fix dup_anon_vma() in vma_merge() case 4") on

Which tree is that?
The mm-hotfixes-stable commit is here:
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/commit/?h=mm-hotfixes-stable&id=4c6759967826b87f56c73e0f1deb7b76379ccd23

> top of linus/master, I don't get this particular failure anymore.
> 
> I do get the "kernel BUG at mm/filemap.c:155!", so it might be masking
> another problem. (Added Matthew to Cc)
> 
> I think the right thing to do is to include Vlastimil's fix.

Great, thanks.

> Thanks,
> Liam
> 
> ...
> 



  reply	other threads:[~2023-03-01 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  7:21 kernel test robot
2023-03-01 16:50 ` Liam R. Howlett
2023-03-01 19:10   ` Vlastimil Babka [this message]
2023-03-01 20:35     ` Liam R. Howlett

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=45eeb539-ed82-4984-197b-3f88cd765a59@suse.cz \
    --to=vbabka@suse.cz \
    --cc=Liam.Howlett@Oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --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