From: Christoph Hellwig <hch@lst.de>
To: Jan Kara <jack@suse.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>, Christoph Hellwig <hch@lst.de>,
Dmitry Monakhov <dmonakhov@openvz.org>,
Jeff Moyer <jmoyer@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-aio@kvack.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] aio: fix a user triggered use after free (and fix freeze protection of aio writes)
Date: Sun, 30 Oct 2016 16:58:06 +0100 [thread overview]
Message-ID: <20161030155806.GA9046@lst.de> (raw)
In-Reply-To: <20161030105231.GA16015@quack2.suse.cz>
On Sun, Oct 30, 2016 at 11:52:31AM +0100, Jan Kara wrote:
> Hum, the additional refcount patch oopses on me when running generic/323,
> I'll have to board to my flight to US shortly so I won't be able to send it
> soon - maybe when I'm transferring in Denver ;).
I've got a version that works and the rest of the patches rebased on top
of it.
And I've also got internet on my flight, so I'll be able to post it as
soon as testing finishes :)
>
> Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
---end quoted text---
next prev parent reply other threads:[~2016-10-30 15:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1477727070-18806-1-git-send-email-hch@lst.de>
2016-10-29 7:44 ` [PATCH] aio: fix a user triggered use after free (and fix freeze protection of aio writes) Christoph Hellwig
2016-10-29 12:24 ` Al Viro
2016-10-29 15:20 ` Christoph Hellwig
2016-10-29 16:12 ` Al Viro
2016-10-29 16:29 ` Al Viro
2016-10-30 6:32 ` Christoph Hellwig
2016-10-29 17:47 ` Linus Torvalds
2016-10-29 18:52 ` Al Viro
2016-10-29 19:07 ` Linus Torvalds
2016-10-29 19:17 ` Al Viro
2016-10-29 20:09 ` Linus Torvalds
2016-10-30 9:44 ` Jan Kara
2016-10-30 10:52 ` Jan Kara
2016-10-30 15:58 ` Christoph Hellwig [this message]
2016-10-30 6:29 ` Christoph Hellwig
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=20161030155806.GA9046@lst.de \
--to=hch@lst.de \
--cc=dmonakhov@openvz.org \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).