public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Josef Bacik <[email protected]>,
	syzbot <[email protected]>
Cc: [email protected], [email protected], [email protected],
	[email protected], [email protected],
	[email protected], [email protected],
	[email protected], [email protected]
Subject: Re: [syzbot] INFO: task hung in io_uring_cancel_generic (2)
Date: Wed, 8 Dec 2021 20:45:27 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 12/8/21 7:51 PM, Josef Bacik wrote:
> On Wed, Dec 08, 2021 at 02:12:09PM -0800, syzbot wrote:
>> syzbot has bisected this issue to:
>>
>> commit 741ec653ab58f5f263f2b6df38157997661c7a50
>> Author: Qu Wenruo <[email protected]>
>> Date:   Mon Sep 27 07:22:01 2021 +0000
>>
>>     btrfs: subpage: make end_compressed_bio_writeback() compatible
>>
> 
> This isn't the right patch, this is x86 so sectorsize == pagesize, so this patch
> didn't change anything at all.  Also unless the local fs is btrfs with
> compression enabled I'm not entirely sure how this would even matter, the
> reproducer seems to be purely io_uring related.  Thanks,

Yeah, it's not btrfs, it's just one of those "bisect gone awry" cases. btrfs
guys can ignore this one.

-- 
Jens Axboe


      reply	other threads:[~2021-12-09  3:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 21:03 [syzbot] INFO: task hung in io_uring_cancel_generic (2) syzbot
2021-12-08  0:04 ` syzbot
2021-12-09 15:58   ` Jens Axboe
2021-12-09 16:56     ` syzbot
2021-12-08 22:12 ` syzbot
2021-12-09  2:51   ` Josef Bacik
2021-12-09  3:45     ` Jens Axboe [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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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