All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: syzbot <syzbot+a1deb5533794ff31868e@syzkaller.appspotmail.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	muchun.song@linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] possible deadlock in __unmap_hugepage_range
Date: Fri, 26 Jan 2024 01:34:06 -0800	[thread overview]
Message-ID: <ZbN8jvab1Orbu/Ui@gmail.com> (raw)
In-Reply-To: <20240126012540.045d8521de02fab64f3cbf78@linux-foundation.org>

On Fri, Jan 26, 2024 at 01:25:40AM -0800, Andrew Morton wrote:
> On Fri, 26 Jan 2024 01:04:29 -0800 syzbot <syzbot+a1deb5533794ff31868e@syzkaller.appspotmail.com> wrote:
> 
> > Hello,
> > 
> > syzbot found the following issue on:
> > 
> > HEAD commit:    8bf1262c53f5 Add linux-next specific files for 20240124
> > git tree:       linux-next
> > console+strace: https://syzkaller.appspot.com/x/log.txt?x=1218a7abe80000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=ff4b59a824278780
> > dashboard link: https://syzkaller.appspot.com/bug?extid=a1deb5533794ff31868e
> > compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=151a9cf7e80000
> > C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=164b70cfe80000
> > 
> > Downloadable assets:
> > disk image: https://storage.googleapis.com/syzbot-assets/7696d711072d/disk-8bf1262c.raw.xz
> > vmlinux: https://storage.googleapis.com/syzbot-assets/92cd47c28072/vmlinux-8bf1262c.xz
> > kernel image: https://storage.googleapis.com/syzbot-assets/add5c7493418/bzImage-8bf1262c.xz
> > 
> > The issue was bisected to:
> > 
> > commit 947b031634e7af3d265275c26ec17e2f96fdb5a1
> > Author: Breno Leitao <leitao@debian.org>
> > Date:   Wed Jan 17 17:10:57 2024 +0000
> > 
> >     mm/hugetlb: restore the reservation if needed
> 
> Thanks.  But moments after I moved this into mm.git's
> mm-hotfixes-stable branch, in preparation for upstreaming.
> 
> I have fully dropped the patches titled
> 
> 	mm/hugetlb: restore the reservation if needed
> 	selftests/mm: run_vmtests.sh: add hugetlb_madv_vs_map
> 

Thanks Andrew. Let me investigate it. I post as I find what's wrong.


      reply	other threads:[~2024-01-26  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26  9:04 [syzbot] [mm?] possible deadlock in __unmap_hugepage_range syzbot
2024-01-26  9:25 ` Andrew Morton
2024-01-26  9:34   ` Breno Leitao [this message]

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=ZbN8jvab1Orbu/Ui@gmail.com \
    --to=leitao@debian.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=syzbot+a1deb5533794ff31868e@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.