From: Lee Jones <lee.jones@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, asml.silence@gmail.com, axboe@kernel.dk,
linux-kernel@vger.kernel.org,
syzbot+b0003676644cf0d6acc4@syzkaller.appspotmail.com
Subject: Re: [PATCH v5.10.y 1/1] Revert "io_uring: reinforce cancel on flush during exit"
Date: Wed, 3 Nov 2021 07:38:10 +0000 [thread overview]
Message-ID: <YYI8YjbE5xTSLLn4@google.com> (raw)
In-Reply-To: <YYFfIk2CQaFI0Zdg@kroah.com>
On Tue, 02 Nov 2021, Greg KH wrote:
> On Tue, Nov 02, 2021 at 03:49:30PM +0000, Lee Jones wrote:
> > This reverts commit 88dbd085a51ec78c83dde79ad63bca8aa4272a9d.
> >
> > Causes the following Syzkaller reported issue:
> >
> > LINK: https://syzkaller.appspot.com/bug?extid=b0003676644cf0d6acc4
>
> "Link:"?
Sure.
> > Reported-by: syzbot+b0003676644cf0d6acc4@syzkaller.appspotmail.com
> > Signed-off-by: Lee Jones <lee.jones@linaro.org>
>
> Why does the patch here cause this error? Is it due to the backport
> being different than what went into Linus's tree, or something else?
The patch is the same.
I need to do some more testing, but I assume it *was* also broken in
Mainline until the whole section was rewritten. Unfortunately, the
patch which does that does not apply to v5.10.y. Again, I can look
into this, but I'm not quite sure how far the rabbit hole goes.
> The original commit did fix a real issue, what should we do now to
> resolve that issue in 5.10.y instead?
Ideally I'd like the original author and/or the domain experts to have
a look and chime in here.
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2021-11-03 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 15:49 [PATCH v5.10.y 1/1] Revert "io_uring: reinforce cancel on flush during exit" Lee Jones
2021-11-02 15:54 ` Greg KH
2021-11-03 7:38 ` Lee Jones [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=YYI8YjbE5xTSLLn4@google.com \
--to=lee.jones@linaro.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+b0003676644cf0d6acc4@syzkaller.appspotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.