linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, Chris Mason <clm@fb.com>,
	Ming Lei <ming.lei@redhat.com>,
	linux-block@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: [BUG] bisected to: block: fix splitting segments on boundary masks
Date: Mon, 13 Jan 2020 22:13:17 -0500	[thread overview]
Message-ID: <20200113221317.0e27f0a9@rorschach.local.home> (raw)

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

Hi!

Running one of my ftrace stress tests, I hit this bug:
(On i386, haven't tested on x86_64 yet)

------------[ cut here ]------------
kernel BUG at block/bio.c:1885!
invalid opcode: 0000 [#1] SMP PTI
CPU: 1 PID: 105 Comm: kworker/u8:6 Not tainted 5.5.0-rc4-test+ #365
Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), BIOS V1.6 02/22/2014
Workqueue: writeback wb_workfn (flush-8:0)
EIP: bio_split+0xf/0x67
Code: 89 d8 e8 90 0f 02 00 85 c0 79 09 89 d8 31 db e8 e0 fa ff ff 89 d8 5b 5e 5f 5d c3 e8 db 5b d2 ff 55 89 e5 57 56 53 85 d2 7f 02 <0f> 0b 8b 58 20 c1 eb 09 39 d3 77 02 0f 0b 89 cb 8b 4d 08 89 d6 89
EAX: e2ddb600 EBX: ec74bc80 ECX: 00000c00 EDX: 00000000
ESI: 00000000 EDI: 00025000 EBP: ec74bbec ESP: ec74bbe0
DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010246
CR0: 80050033 CR2: 025c7ed4 CR3: 270bc000 CR4: 001406f0
Call Trace:
 __blk_queue_split+0x327/0x40b
 ? blk_mq_try_issue_directly+0x91/0x91
 ? blk_mq_try_issue_directly+0x91/0x91
 blk_mq_make_request+0x6e/0x407
 ? function_trace_call+0xb8/0xdc
 ? blk_mq_try_issue_directly+0x91/0x91
 generic_make_request+0xc7/0x1e1
 submit_bio+0x113/0x12b
 ? ftrace_call+0x5/0x15
 ext4_io_submit+0x47/0x51
 ext4_writepages+0x53d/0x6ee
 ? trace_function+0xcc/0xd4
 ? page_writeback_cpu_online+0x11/0x11
 do_writepages+0x29/0x55
 __writeback_single_inode+0xc4/0x420
 writeback_sb_inodes+0x239/0x395
 __writeback_inodes_wb+0x5c/0x8b
 ? trace_trigger_soft_disabled+0x40/0x40
 wb_writeback+0x175/0x30a
 wb_workfn+0x255/0x348
 ? function_trace_call+0xb8/0xdc
 ? inode_wait_for_writeback+0x28/0x28
 process_one_work+0x25e/0x3d1
 worker_thread+0x170/0x21f
 kthread+0xe1/0xe3
 ? rescuer_thread+0x217/0x217
 ? kthread_worker_fn+0x116/0x116
 ret_from_fork+0x2e/0x38
Modules linked in: ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipv6 crc_ccitt realtek ppdev r8169 parport_pc parport
---[ end trace 7b7d4d993e5ceea3 ]---

It is very reproducible and I bisected it to 429120f3df2dba ("block: fix
splitting segments on boundary masks")

The test is simply:

 # perf record -o perf-test.dat -a -- \
   trace-cmd record -e all -p function ./hackbench 20
 # trace-cmd report > /tmp/tempfile

It appears to crash on the trace-cmd report.

Attached is the config.

-- Steve

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33049 bytes --]

             reply	other threads:[~2020-01-14  3:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14  3:13 Steven Rostedt [this message]
2020-01-14  4:09 ` [BUG] bisected to: block: fix splitting segments on boundary masks Jens Axboe
2020-01-14 20:34   ` Steven Rostedt
2020-01-14 20:38     ` Jens Axboe

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=20200113221317.0e27f0a9@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=axboe@kernel.dk \
    --cc=clm@fb.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).