io-uring.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hao Sun <sunhao.th@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Pavel Begunkov <asml.silence@gmail.com>,
	io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: INFO: task hung in io_uring_cancel_generic
Date: Mon, 13 Sep 2021 11:21:57 +0800	[thread overview]
Message-ID: <CACkBjsYGnmLfCV2bNb45WhBiC-DqAvWjP1rb_6fxVZe5hqzOCw@mail.gmail.com> (raw)
In-Reply-To: <9b5d8c00-0191-895b-0556-2f8167ab52bd@kernel.dk>

> Jens Axboe <axboe@kernel.dk> 于2021年9月13日周一 上午10:50写道:
>
> On 9/12/21 8:26 PM, Hao Sun wrote:
> > Hi
> >
> > Healer found a C reproducer for this crash ("INFO: task hung in
> > io_ring_exit_work").
> >
> > HEAD commit: 4b93c544e90e-thunderbolt: test: split up test cases
>
> Does this reproduce on 5.15-rc1? We had a few hang cases fixed for io-wq
> since that commit 6 days ago.

Just tried it. No, it did not crash the kernel on 5.15-rc1.
Following log was printed repeatedly:
[  647.478557][ T6807]  loop0: p1 p2 < > p3 p4
[  647.478922][ T6807] loop0: p1 size 11290111 extends beyond EOD, truncated
[  647.481111][ T6807] loop0: p3 size 1914664839 extends beyond EOD, truncated
[  647.482512][ T6807] loop0: p4 size 3389030400 extends beyond EOD, truncated

It seems that this crash was fixed. Sorry for the dup report.

>
> --
> Jens Axboe
>

  reply	other threads:[~2021-09-13  3:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07 11:50 Hao Sun
2021-09-07 19:30 ` Jens Axboe
2021-09-07 21:31   ` Pavel Begunkov
2021-09-08  1:01     ` Hao Sun
2021-09-08  6:57       ` Hao Sun
2021-09-08 20:16         ` Pavel Begunkov
2021-09-13  2:26           ` Hao Sun
2021-09-13  2:50             ` Jens Axboe
2021-09-13  3:21               ` Hao Sun [this message]
2021-09-13  8:30             ` Pavel Begunkov
2021-09-14  3:01               ` Hao Sun

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=CACkBjsYGnmLfCV2bNb45WhBiC-DqAvWjP1rb_6fxVZe5hqzOCw@mail.gmail.com \
    --to=sunhao.th@gmail.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: INFO: task hung in io_uring_cancel_generic' \
    /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

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