From: Li Zefan <lizefan@huawei.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Jan Kara <jack@suse.cz>, <linux-fsdevel@vger.kernel.org>,
<xfs@oss.sgi.com>, <linux-ext4@vger.kernel.org>,
<ocfs2-devel@oss.oracle.com>
Subject: Re: [PATCH 0/4 v2] Fix possible use after free with AIO
Date: Thu, 31 Jan 2013 10:10:17 +0800 [thread overview]
Message-ID: <5109D289.1050708@huawei.com> (raw)
In-Reply-To: <20130130144535.GK4503@ZenIV.linux.org.uk>
On 2013/1/30 22:45, Al Viro wrote:
> On Wed, Jan 30, 2013 at 12:27:57AM +0100, Jan Kara wrote:
>>
>> Hi,
>>
>> since nobody seem to have picked up any of the patches (at least
>> nobody told me so), I've added acks I received to the patches and I'm
>> sending them to Al for merging. Al, can you please merge these? Thanks.
>
> VFS part (4/4) picked; IMO at least ext* and xfs should go through the
> filesystem trees. If ocfs2 folks don't pick fs/ocfs2 part, I'll grab
> it as well - not sure how active their tree is these days...
I would say just grab it.
We've been sending bug fixes to ocfs2 mailing list since Aug 2012, but none
was pushed into upstream.
WARNING: multiple messages have this Message-ID (diff)
From: Li Zefan <lizefan@huawei.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Jan Kara <jack@suse.cz>,
ocfs2-devel@oss.oracle.com, xfs@oss.sgi.com
Subject: Re: [PATCH 0/4 v2] Fix possible use after free with AIO
Date: Thu, 31 Jan 2013 10:10:17 +0800 [thread overview]
Message-ID: <5109D289.1050708@huawei.com> (raw)
In-Reply-To: <20130130144535.GK4503@ZenIV.linux.org.uk>
On 2013/1/30 22:45, Al Viro wrote:
> On Wed, Jan 30, 2013 at 12:27:57AM +0100, Jan Kara wrote:
>>
>> Hi,
>>
>> since nobody seem to have picked up any of the patches (at least
>> nobody told me so), I've added acks I received to the patches and I'm
>> sending them to Al for merging. Al, can you please merge these? Thanks.
>
> VFS part (4/4) picked; IMO at least ext* and xfs should go through the
> filesystem trees. If ocfs2 folks don't pick fs/ocfs2 part, I'll grab
> it as well - not sure how active their tree is these days...
I would say just grab it.
We've been sending bug fixes to ocfs2 mailing list since Aug 2012, but none
was pushed into upstream.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Li Zefan <lizefan@huawei.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com,
linux-ext4@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/4 v2] Fix possible use after free with AIO
Date: Thu, 31 Jan 2013 10:10:17 +0800 [thread overview]
Message-ID: <5109D289.1050708@huawei.com> (raw)
In-Reply-To: <20130130144535.GK4503@ZenIV.linux.org.uk>
On 2013/1/30 22:45, Al Viro wrote:
> On Wed, Jan 30, 2013 at 12:27:57AM +0100, Jan Kara wrote:
>>
>> Hi,
>>
>> since nobody seem to have picked up any of the patches (at least
>> nobody told me so), I've added acks I received to the patches and I'm
>> sending them to Al for merging. Al, can you please merge these? Thanks.
>
> VFS part (4/4) picked; IMO at least ext* and xfs should go through the
> filesystem trees. If ocfs2 folks don't pick fs/ocfs2 part, I'll grab
> it as well - not sure how active their tree is these days...
I would say just grab it.
We've been sending bug fixes to ocfs2 mailing list since Aug 2012, but none
was pushed into upstream.
next prev parent reply other threads:[~2013-01-31 2:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 23:27 [PATCH 0/4 v2] Fix possible use after free with AIO Jan Kara
2013-01-29 23:27 ` [Ocfs2-devel] " Jan Kara
2013-01-29 23:27 ` [PATCH 1/4] ext4: Fix possible use-after-free " Jan Kara
2013-01-29 23:27 ` [Ocfs2-devel] " Jan Kara
2013-01-29 23:27 ` Jan Kara
2013-01-30 3:51 ` Theodore Ts'o
2013-01-30 3:51 ` [Ocfs2-devel] " Theodore Ts'o
2013-01-30 3:51 ` Theodore Ts'o
2013-01-29 23:27 ` [PATCH 2/4] xfs: " Jan Kara
2013-01-29 23:27 ` [Ocfs2-devel] " Jan Kara
2013-01-29 23:27 ` Jan Kara
2013-01-30 0:56 ` Ben Myers
2013-01-30 0:57 ` [Ocfs2-devel] " Ben Myers
2013-01-30 0:56 ` Ben Myers
2013-01-29 23:28 ` [PATCH 3/4] ocfs2: " Jan Kara
2013-01-29 23:28 ` [Ocfs2-devel] " Jan Kara
2013-01-29 23:28 ` Jan Kara
2013-01-29 23:28 ` [PATCH 4/4] fs: " Jan Kara
2013-01-29 23:28 ` [Ocfs2-devel] " Jan Kara
2013-01-29 23:28 ` Jan Kara
2013-01-30 14:45 ` [PATCH 0/4 v2] Fix possible use after free " Al Viro
2013-01-30 14:45 ` [Ocfs2-devel] " Al Viro
2013-01-30 14:45 ` Al Viro
2013-01-31 2:10 ` Li Zefan [this message]
2013-01-31 2:10 ` [Ocfs2-devel] " Li Zefan
2013-01-31 2:10 ` Li Zefan
2013-01-31 19:31 ` Joel Becker
2013-01-31 19:31 ` [Ocfs2-devel] " Joel Becker
2013-01-31 19:31 ` Joel Becker
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=5109D289.1050708@huawei.com \
--to=lizefan@huawei.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=viro@ZenIV.linux.org.uk \
--cc=xfs@oss.sgi.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.