From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH] ext4: fix a bug when we try to open a file with O_TMPFILE flag
Date: Sat, 20 Jul 2013 00:36:13 +0100 [thread overview]
Message-ID: <20130719233613.GH4165@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20130719121405.GA3856@gmail.com>
On Fri, Jul 19, 2013 at 08:14:05PM +0800, Zheng Liu wrote:
> Hi Dave,
>
> After applied this patch, the problem has been fixed in my own sand box.
> But that would be great if you could give it a try. I want to make sure
> that this patch can fix the problem. It looks like there has the same
> problem in ext3. So if this patch is fine, I will generate a patch for
> ext3 file system.
Nice catch, and you have my ACK. Which tree do you prefer that to go
through? vfs and ext4 are the obvious candidates...
next prev parent reply other threads:[~2013-07-19 23:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 16:19 kernel BUG at fs/ext4/namei.c:2572! Dave Jones
2013-07-19 1:17 ` Zheng Liu
2013-07-19 12:14 ` [PATCH] ext4: fix a bug when we try to open a file with O_TMPFILE flag Zheng Liu
2013-07-19 19:31 ` Darrick J. Wong
2013-07-19 20:01 ` Dave Jones
2013-07-19 23:36 ` Al Viro [this message]
2013-07-20 16:37 ` Zheng Liu
2013-07-21 0:56 ` Theodore Ts'o
2013-07-21 2:45 ` [GIT PULL] " Theodore Ts'o
2013-07-21 3:16 ` Linus Torvalds
2013-07-23 7:51 ` jon ernst
2013-07-23 9:59 ` Zheng Liu
2013-07-23 13:39 ` jon ernst
2013-07-23 23:38 ` Zheng Liu
2013-07-24 21:58 ` jon ernst
2013-07-25 0:13 ` [PATCH] vfs: add missing check for __O_TMPFILE in fcntl_init() (Re: [PATCH] ext4: fix...) Zheng Liu
2013-07-25 1:17 ` jon ernst
2013-07-29 6:17 ` Zheng Liu
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=20130719233613.GH4165@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=davej@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).