From: Al Viro <viro@zeniv.linux.org.uk>
To: zhengbin <zhengbin13@huawei.com>
Cc: bcrl@kvack.org, linux-fsdevel@vger.kernel.org,
linux-aio@kvack.org, houtao1@huawei.com, yi.zhang@huawei.com
Subject: Re: [PATCH] fix syzkaller task hung in exit_aio
Date: Thu, 7 Mar 2019 00:07:55 +0000 [thread overview]
Message-ID: <20190307000755.GX2217@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20190306194455.GV2217@ZenIV.linux.org.uk>
On Wed, Mar 06, 2019 at 07:44:55PM +0000, Al Viro wrote:
> Leak on error is real (see thread a few days ago), and overall logics for
> "woken" should be similar to what you suggest, but I'd rather handle it
> slightly differently (see the same thread).
>
> I've a patch that ought to fix that and it seems to survive testing; I'll
> post once I finish carving it up - too many cleanups mixed into it. Give
> me a couple of hours; should be done (and posted) by then.
Carved up and posted - sorry, too longer than I hoped ;-/
prev parent reply other threads:[~2019-03-07 0:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 13:53 [PATCH] fix syzkaller task hung in exit_aio zhengbin
2019-03-06 19:44 ` Al Viro
2019-03-07 0:07 ` Al Viro [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=20190307000755.GX2217@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=bcrl@kvack.org \
--cc=houtao1@huawei.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=yi.zhang@huawei.com \
--cc=zhengbin13@huawei.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;
as well as URLs for NNTP newsgroup(s).