From: Breno Leitao <leitao@debian.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: paulmck@kernel.org,
linux-block@vger.kernel.org (open list:BLOCK LAYER),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH] block: Annotate a racy read in blk_do_io_stat()
Date: Fri, 10 May 2024 07:19:18 -0700 [thread overview]
Message-ID: <20240510141921.883231-1-leitao@debian.org> (raw)
KCSAN has reported a potential data race in blk_mq subsystem where
reading the rq->flag.
BUG: KCSAN: data-race in __blk_mq_end_request / blk_mq_check_inflight
read-write to 0xffff888120514d1c of 4 bytes by interrupt on cpu 6:
__blk_mq_end_request (block/blk-mq.c:700 block/blk-mq.c:1040)
scsi_end_request (drivers/scsi/scsi_lib.c:667)
scsi_io_completion (drivers/scsi/scsi_lib.c:1068)
scsi_finish_command (drivers/scsi/scsi.c:199)
scsi_complete (drivers/scsi/scsi_lib.c:?)
blk_done_softirq (block/blk-mq.c:? block/blk-mq.c:1134)
handle_softirqs (./arch/x86/include/asm/jump_label.h:27
./include/linux/jump_label.h:207
./include/trace/events/irq.h:142 kernel/softirq.c:555)
__irq_exit_rcu (kernel/softirq.c:617 kernel/softirq.c:639)
irq_exit_rcu (kernel/softirq.c:651)
common_interrupt (arch/x86/kernel/irq.c:247)
asm_common_interrupt (./arch/x86/include/asm/idtentry.h:693)
cpuidle_enter_state (drivers/cpuidle/cpuidle.c:291)
cpuidle_enter (drivers/cpuidle/cpuidle.c:388)
do_idle (kernel/sched/idle.c:155 kernel/sched/idle.c:236
kernel/sched/idle.c:332)
cpu_startup_entry (kernel/sched/idle.c:429)
start_secondary (arch/x86/kernel/smpboot.c:313)
common_startup_64 (arch/x86/kernel/head_64.S:421)
read to 0xffff888120514d1c of 4 bytes by task 9106 on cpu 51:
blk_mq_check_inflight (block/blk.h:356 block/blk-mq.c:94)
14:06:18 bt_iter (block/blk-mq-tag.c:292)
sbitmap_for_each_set (./include/linux/sbitmap.h:284
./include/linux/sbitmap.h:302)
blk_mq_queue_tag_busy_iter (block/blk-mq-tag.c:? block/blk-mq-tag.c:533)
blk_mq_in_flight (block/blk-mq.c:109)
diskstats_show (block/genhd.c:?)
seq_read_iter (fs/seq_file.c:?)
proc_reg_read_iter (fs/proc/inode.c:299)
vfs_read (fs/read_write.c:396 fs/read_write.c:476)
ksys_read (fs/read_write.c:619)
__x64_sys_read (fs/read_write.c:627)
x64_sys_call (arch/x86/entry/syscall_64.c:33)
do_syscall_64 (arch/x86/entry/common.c:?)
entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)
value changed: 0x00022382 -> 0x00022182
Discussing it with Jens Axboe and Pavel Begunkov, they suggested we just
want to annotated this with data_race(), since disk statistic reading
isn't critical, and it will not be a big deal if this bit is not stable.
Suggested-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Breno Leitao <leitao@debian.org>
---
block/blk.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/block/blk.h b/block/blk.h
index d9f584984bc4..57a1d73a0718 100644
--- a/block/blk.h
+++ b/block/blk.h
@@ -353,7 +353,8 @@ int blk_dev_init(void);
*/
static inline bool blk_do_io_stat(struct request *rq)
{
- return (rq->rq_flags & RQF_IO_STAT) && !blk_rq_is_passthrough(rq);
+ /* Disk stats reading isn’t critical, let it race */
+ return (data_race(rq->rq_flags) & RQF_IO_STAT) && !blk_rq_is_passthrough(rq);
}
void update_io_ticks(struct block_device *part, unsigned long now, bool end);
--
2.43.0
next reply other threads:[~2024-05-10 14:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 14:19 Breno Leitao [this message]
2024-05-10 14:28 ` [PATCH] block: Annotate a racy read in blk_do_io_stat() Bart Van Assche
2024-05-10 14:57 ` Breno Leitao
2024-05-10 15:41 ` Paul E. McKenney
2024-05-10 16:20 ` Bart Van Assche
2024-05-10 17:08 ` Paul E. McKenney
2024-05-10 20:30 ` Bart Van Assche
2024-05-10 22:35 ` Paul E. McKenney
2024-05-10 23:22 ` Bart Van Assche
2024-05-11 0:41 ` Paul E. McKenney
2024-05-13 8:13 ` Marco Elver
2024-05-14 23:47 ` Paul E. McKenney
2024-05-15 7:58 ` Marco Elver
2024-05-15 12:48 ` Breno Leitao
2024-05-15 13:20 ` Marco Elver
2024-05-15 15:57 ` Paul E. McKenney
2024-05-15 17:40 ` Marco Elver
2024-05-15 21:51 ` Paul E. McKenney
2024-05-16 6:35 ` Marco Elver
2024-05-20 18:05 ` Paul E. McKenney
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=20240510141921.883231-1-leitao@debian.org \
--to=leitao@debian.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).