All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: syzbot <syzbot+9ce464e21fc2ab95dbf3@syzkaller.appspotmail.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: kworker/u4:LINE/41
Date: Mon, 8 Jun 2020 00:23:49 +1000	[thread overview]
Message-ID: <20200608002349.085eac93@canb.auug.org.au> (raw)
In-Reply-To: <00000000000082afe105a77c949d@google.com>

[-- Attachment #1: Type: text/plain, Size: 9034 bytes --]

Hi syzbot,

On Sun, 07 Jun 2020 04:13:12 -0700 syzbot <syzbot+9ce464e21fc2ab95dbf3@syzkaller.appspotmail.com> wrote:
>
> Hello,
> 
> syzbot found the following crash on:
> 
> HEAD commit:    48f99181 Add linux-next specific files for 20200603
> git tree:       linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=16a4c051100000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=365f706273eaf502
> dashboard link: https://syzkaller.appspot.com/bug?extid=9ce464e21fc2ab95dbf3
> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> 
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+9ce464e21fc2ab95dbf3@syzkaller.appspotmail.com
> 
> BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u4:2/41
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 0 PID: 41 Comm: kworker/u4:2 Not tainted 5.7.0-next-20200603-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
> Workqueue: writeback wb_workfn (flush-8:0)
> Call Trace:
>  __dump_stack lib/dump_stack.c:77 [inline]
>  dump_stack+0x18f/0x20d lib/dump_stack.c:118
>  check_preemption_disabled+0x20d/0x220 lib/smp_processor_id.c:48
>  ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
>  ext4_ext_map_blocks+0x201b/0x33e0 fs/ext4/extents.c:4244
>  ext4_map_blocks+0x4cb/0x1640 fs/ext4/inode.c:626
>  mpage_map_one_extent fs/ext4/inode.c:2377 [inline]
>  mpage_map_and_submit_extent fs/ext4/inode.c:2430 [inline]
>  ext4_writepages+0x1ab5/0x3400 fs/ext4/inode.c:2782
>  do_writepages+0xfa/0x2a0 mm/page-writeback.c:2354
>  __writeback_single_inode+0x12a/0x13d0 fs/fs-writeback.c:1452
>  writeback_sb_inodes+0x515/0xdc0 fs/fs-writeback.c:1716
>  __writeback_inodes_wb+0xc3/0x250 fs/fs-writeback.c:1785
>  wb_writeback+0x8db/0xd50 fs/fs-writeback.c:1894
>  wb_check_old_data_flush fs/fs-writeback.c:1996 [inline]
>  wb_do_writeback fs/fs-writeback.c:2049 [inline]
>  wb_workfn+0xab3/0x1090 fs/fs-writeback.c:2078
>  process_one_work+0x965/0x1690 kernel/workqueue.c:2269
>  worker_thread+0x96/0xe10 kernel/workqueue.c:2415
>  kthread+0x3b5/0x4a0 kernel/kthread.c:291
>  ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293
> BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u4:2/41
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 0 PID: 41 Comm: kworker/u4:2 Not tainted 5.7.0-next-20200603-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
> Workqueue: writeback wb_workfn (flush-8:0)
> Call Trace:
>  __dump_stack lib/dump_stack.c:77 [inline]
>  dump_stack+0x18f/0x20d lib/dump_stack.c:118
>  check_preemption_disabled+0x20d/0x220 lib/smp_processor_id.c:48
>  ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
>  ext4_ext_map_blocks+0x201b/0x33e0 fs/ext4/extents.c:4244
>  ext4_map_blocks+0x4cb/0x1640 fs/ext4/inode.c:626
>  mpage_map_one_extent fs/ext4/inode.c:2377 [inline]
>  mpage_map_and_submit_extent fs/ext4/inode.c:2430 [inline]
>  ext4_writepages+0x1ab5/0x3400 fs/ext4/inode.c:2782
>  do_writepages+0xfa/0x2a0 mm/page-writeback.c:2354
>  __writeback_single_inode+0x12a/0x13d0 fs/fs-writeback.c:1452
>  writeback_sb_inodes+0x515/0xdc0 fs/fs-writeback.c:1716
>  __writeback_inodes_wb+0xc3/0x250 fs/fs-writeback.c:1785
>  wb_writeback+0x8db/0xd50 fs/fs-writeback.c:1894
>  wb_check_old_data_flush fs/fs-writeback.c:1996 [inline]
>  wb_do_writeback fs/fs-writeback.c:2049 [inline]
>  wb_workfn+0xab3/0x1090 fs/fs-writeback.c:2078
>  process_one_work+0x965/0x1690 kernel/workqueue.c:2269
>  worker_thread+0x96/0xe10 kernel/workqueue.c:2415
>  kthread+0x3b5/0x4a0 kernel/kthread.c:291
>  ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293
> BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u4:2/41
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 0 PID: 41 Comm: kworker/u4:2 Not tainted 5.7.0-next-20200603-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
> Workqueue: writeback wb_workfn (flush-8:0)
> Call Trace:
>  __dump_stack lib/dump_stack.c:77 [inline]
>  dump_stack+0x18f/0x20d lib/dump_stack.c:118
>  check_preemption_disabled+0x20d/0x220 lib/smp_processor_id.c:48
>  ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
>  ext4_ext_map_blocks+0x201b/0x33e0 fs/ext4/extents.c:4244
>  ext4_map_blocks+0x4cb/0x1640 fs/ext4/inode.c:626
>  mpage_map_one_extent fs/ext4/inode.c:2377 [inline]
>  mpage_map_and_submit_extent fs/ext4/inode.c:2430 [inline]
>  ext4_writepages+0x1ab5/0x3400 fs/ext4/inode.c:2782
>  do_writepages+0xfa/0x2a0 mm/page-writeback.c:2354
>  __writeback_single_inode+0x12a/0x13d0 fs/fs-writeback.c:1452
>  writeback_sb_inodes+0x515/0xdc0 fs/fs-writeback.c:1716
>  __writeback_inodes_wb+0xc3/0x250 fs/fs-writeback.c:1785
>  wb_writeback+0x8db/0xd50 fs/fs-writeback.c:1894
>  wb_check_old_data_flush fs/fs-writeback.c:1996 [inline]
>  wb_do_writeback fs/fs-writeback.c:2049 [inline]
>  wb_workfn+0xab3/0x1090 fs/fs-writeback.c:2078
>  process_one_work+0x965/0x1690 kernel/workqueue.c:2269
>  worker_thread+0x96/0xe10 kernel/workqueue.c:2415
>  kthread+0x3b5/0x4a0 kernel/kthread.c:291
>  ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293
> BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u4:2/41
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 1 PID: 41 Comm: kworker/u4:2 Not tainted 5.7.0-next-20200603-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
> Workqueue: writeback wb_workfn (flush-8:0)
> Call Trace:
>  __dump_stack lib/dump_stack.c:77 [inline]
>  dump_stack+0x18f/0x20d lib/dump_stack.c:118
>  check_preemption_disabled+0x20d/0x220 lib/smp_processor_id.c:48
>  ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
>  ext4_ext_map_blocks+0x201b/0x33e0 fs/ext4/extents.c:4244
>  ext4_map_blocks+0x4cb/0x1640 fs/ext4/inode.c:626
>  mpage_map_one_extent fs/ext4/inode.c:2377 [inline]
>  mpage_map_and_submit_extent fs/ext4/inode.c:2430 [inline]
>  ext4_writepages+0x1ab5/0x3400 fs/ext4/inode.c:2782
>  do_writepages+0xfa/0x2a0 mm/page-writeback.c:2354
>  __writeback_single_inode+0x12a/0x13d0 fs/fs-writeback.c:1452
>  writeback_sb_inodes+0x515/0xdc0 fs/fs-writeback.c:1716
>  __writeback_inodes_wb+0xc3/0x250 fs/fs-writeback.c:1785
>  wb_writeback+0x8db/0xd50 fs/fs-writeback.c:1894
>  wb_check_old_data_flush fs/fs-writeback.c:1996 [inline]
>  wb_do_writeback fs/fs-writeback.c:2049 [inline]
>  wb_workfn+0xab3/0x1090 fs/fs-writeback.c:2078
>  process_one_work+0x965/0x1690 kernel/workqueue.c:2269
>  worker_thread+0x96/0xe10 kernel/workqueue.c:2415
>  kthread+0x3b5/0x4a0 kernel/kthread.c:291
>  ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293
> BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u4:2/41
> caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
> CPU: 1 PID: 41 Comm: kworker/u4:2 Not tainted 5.7.0-next-20200603-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
> Workqueue: writeback wb_workfn (flush-8:0)
> Call Trace:
>  __dump_stack lib/dump_stack.c:77 [inline]
>  dump_stack+0x18f/0x20d lib/dump_stack.c:118
>  check_preemption_disabled+0x20d/0x220 lib/smp_processor_id.c:48
>  ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
>  ext4_ext_map_blocks+0x201b/0x33e0 fs/ext4/extents.c:4244
>  ext4_map_blocks+0x4cb/0x1640 fs/ext4/inode.c:626
>  mpage_map_one_extent fs/ext4/inode.c:2377 [inline]
>  mpage_map_and_submit_extent fs/ext4/inode.c:2430 [inline]
>  ext4_writepages+0x1ab5/0x3400 fs/ext4/inode.c:2782
>  do_writepages+0xfa/0x2a0 mm/page-writeback.c:2354
>  __writeback_single_inode+0x12a/0x13d0 fs/fs-writeback.c:1452
>  writeback_sb_inodes+0x515/0xdc0 fs/fs-writeback.c:1716
>  __writeback_inodes_wb+0xc3/0x250 fs/fs-writeback.c:1785
>  wb_writeback+0x8db/0xd50 fs/fs-writeback.c:1894
>  wb_check_old_data_flush fs/fs-writeback.c:1996 [inline]
>  wb_do_writeback fs/fs-writeback.c:2049 [inline]
>  wb_workfn+0xab3/0x1090 fs/fs-writeback.c:2078
>  process_one_work+0x965/0x1690 kernel/workqueue.c:2269
>  worker_thread+0x96/0xe10 kernel/workqueue.c:2415
>  kthread+0x3b5/0x4a0 kernel/kthread.c:291
>  ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293
> tipc: TX() has been purged, node left!
> 
> 
> ---
> This bug is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkaller@googlegroups.com.
> 
> syzbot will keep track of this bug report. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

#syz dup: linux-next test error: BUG: using smp_processor_id() in preemptible  [ADDR] code: syz-fuzzer/6792

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2020-06-07 14:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-07 11:13 linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: kworker/u4:LINE/41 syzbot
2020-06-07 14:23 ` Stephen Rothwell [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=20200608002349.085eac93@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=syzbot+9ce464e21fc2ab95dbf3@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    /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.