[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6729f73d.050a0220.2edce.1509.GAE@google.com>
Date: Tue, 05 Nov 2024 02:45:17 -0800
From: syzbot <syzbot+949ae54e95a2fab4cbb4@...kaller.appspotmail.com>
To: hdanton@...a.com
Cc: hdanton@...a.com, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [block?] possible deadlock in __submit_bio
> On Sun, 03 Nov 2024 14:19:28 -0800
>> syzbot found the following issue on:
>>
>> HEAD commit: f9f24ca362a4 Add linux-next specific files for 20241031
>> git tree: linux-next
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16749340580000
>
> #syz test linux-nex f9f24ca362a4
"linux-nex" does not look like a valid git repo address.
>
> --- x/block/blk.h
> +++ y/block/blk.h
> @@ -72,8 +72,6 @@ static inline int bio_queue_enter(struct
> struct request_queue *q = bdev_get_queue(bio->bi_bdev);
>
> if (blk_try_enter_queue(q, false)) {
> - rwsem_acquire_read(&q->io_lockdep_map, 0, 0, _RET_IP_);
> - rwsem_release(&q->io_lockdep_map, _RET_IP_);
> return 0;
> }
> return __bio_queue_enter(q, bio);
> --- x/block/blk-core.c
> +++ y/block/blk-core.c
> @@ -358,8 +358,6 @@ int __bio_queue_enter(struct request_que
> goto dead;
> }
>
> - rwsem_acquire_read(&q->io_lockdep_map, 0, 0, _RET_IP_);
> - rwsem_release(&q->io_lockdep_map, _RET_IP_);
> return 0;
> dead:
> bio_io_error(bio);
> --
Powered by blists - more mailing lists