mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+949ae54e95a2fab4cbb4@syzkaller.appspotmail.com>
To: hdanton@sina.com
Cc: hdanton@sina.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] possible deadlock in __submit_bio
Date: Tue, 05 Nov 2024 02:45:17 -0800	[thread overview]
Message-ID: <6729f73d.050a0220.2edce.1509.GAE@google.com> (raw)
In-Reply-To: <20241105104500.3206-1-hdanton@sina.com>

> 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);
> --

  reply	other threads:[~2024-11-05 10:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-03 22:19 syzbot
2024-11-04 11:27 ` Hillf Danton
2024-11-05 10:45 ` Hillf Danton
2024-11-05 10:45   ` syzbot [this message]
2024-11-05 11:35 ` Hillf Danton
2024-11-05 21:23   ` syzbot

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=6729f73d.050a0220.2edce.1509.GAE@google.com \
    --to=syzbot+949ae54e95a2fab4cbb4@syzkaller.appspotmail.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome