From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH 0/2] 5.16 fixes for syz reports
Date: Fri, 26 Nov 2021 08:36:53 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Fri, 26 Nov 2021 14:38:13 +0000, Pavel Begunkov wrote:
> The second patch fixes the last five reports, i.e. deadlocks and
> inconsistent irq state, all of the caused by the same patch and
> are dups of each other.
>
> 1/2 is for another report, where tw of cancellation requests don't
> handle PF_EXITING.
>
> [...]
Applied, thanks!
[1/2] io_uring: fail cancellation for EXITING tasks
commit: 617a89484debcd4e7999796d693cf0b77d2519de
[2/2] io_uring: fix link traversal locking
commit: 6af3f48bf6156a7f02e91aca64e2927c4bebda03
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2021-11-26 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 14:38 [PATCH 0/2] 5.16 fixes for syz reports Pavel Begunkov
2021-11-26 14:38 ` [PATCH 1/2] io_uring: fail cancellation for EXITING tasks Pavel Begunkov
2021-11-26 15:32 ` Pavel Begunkov
2021-11-26 14:38 ` [PATCH 2/2] io_uring: fix link traversal locking Pavel Begunkov
2021-11-26 15:29 ` Pavel Begunkov
2021-11-26 15:36 ` 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 \
--in-reply-to=163794101368.606591.5665140915720222853.b4-ty@kernel.dk \
[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