All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lstoakes@gmail.com>
To: syzbot <syzbot+6d9043ea38ed2b9ef000@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, djwong@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] BUG: sleeping function called from invalid context in vm_map_ram
Date: Wed, 22 Mar 2023 05:41:34 +0000	[thread overview]
Message-ID: <CAA5enKbNWqTp13a6dgkbm+aDY-PBr24x=aGXz6=JUxc0OM1UPg@mail.gmail.com> (raw)
In-Reply-To: <00000000000056cdc905f76c0733@google.com>

On Tue, 21 Mar 2023 at 17:03, syzbot
<syzbot+6d9043ea38ed2b9ef000@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:    73f2c2a7e1d2 Add linux-next specific files for 20230320
> git tree:       linux-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=11ad6e1cc80000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=f22105589e896af1
> dashboard link: https://syzkaller.appspot.com/bug?extid=6d9043ea38ed2b9ef000
> compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17d199bac80000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=159c7281c80000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/2e4e105e18cf/disk-73f2c2a7.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/08d761112297/vmlinux-73f2c2a7.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/4b39e3e871ce/bzImage-73f2c2a7.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/662e0db5efdd/mount_0.gz
>
> The issue was bisected to:
>
> commit 8f4977bdd77ee3dce8af81488231e7535695f889
> Author: Lorenzo Stoakes <lstoakes@gmail.com>
> Date:   Sun Mar 19 07:09:31 2023 +0000
>
>     mm: vmalloc: use rwsem, mutex for vmap_area_lock and vmap_block->lock

This patch has already been dropped in mm-unstable which will
eventually reach linux-next. The current revision of this patch set
retains the spinlocks.

[snip]

-- 
Lorenzo Stoakes
https://ljs.io

      reply	other threads:[~2023-03-22  5:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 17:03 [syzbot] [xfs?] BUG: sleeping function called from invalid context in vm_map_ram syzbot
2023-03-22  5:41 ` Lorenzo Stoakes [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='CAA5enKbNWqTp13a6dgkbm+aDY-PBr24x=aGXz6=JUxc0OM1UPg@mail.gmail.com' \
    --to=lstoakes@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=djwong@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=syzbot+6d9043ea38ed2b9ef000@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.