From: Theodore Ts'o <tytso@mit.edu>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Linux Filesystem Development List <linux-fsdevel@vger.kernel.org>,
jaegeuk@kernel.org
Subject: Re: [PATCH 0/5] Miklos's vfs/nfs/ext4 patches in the ext4.git tree
Date: Mon, 28 Mar 2016 08:36:16 -0400 [thread overview]
Message-ID: <20160328123616.GA3321@thunk.org> (raw)
In-Reply-To: <CA+icZUWgxMNjchWAxzsBxMsjbpsoZMng6U4t7heUGkiyxkH=jw@mail.gmail.com>
On Sun, Mar 27, 2016 at 09:31:58PM +0200, Sedat Dilek wrote:
> v4.5 ?
>
> ext4: use file_dentry()
> Cc: <stable@vger.kernel.org> # v4.5
This only became a problem in:
Fixes: ff978b09f973 ("ext4 crypto: move context consistency check to ext4_file_open()")
which showed up in v4.5. In fact that commit won't apply previous to
4.5.
- Ted
next prev parent reply other threads:[~2016-03-28 12:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 21:09 [PATCH 0/5] Miklos's vfs/nfs/ext4 patches in the ext4.git tree Theodore Ts'o
2016-03-26 21:09 ` [PATCH 1/5] fs: add file_dentry() Theodore Ts'o
2016-03-26 21:09 ` [PATCH 2/5] nfs: use file_dentry() Theodore Ts'o
2016-03-26 21:09 ` [PATCH 3/5] ext4: use dget_parent() in ext4_file_open() Theodore Ts'o
2016-03-26 21:09 ` [PATCH 4/5] ext4: use file_dentry() Theodore Ts'o
2016-03-26 21:10 ` [PATCH 5/5] ext4 crypto: use dget_parent() in ext4_d_revalidate() Theodore Ts'o
2016-03-27 8:02 ` Sedat Dilek
2016-03-27 18:16 ` Theodore Ts'o
2016-03-27 8:06 ` [PATCH 0/5] Miklos's vfs/nfs/ext4 patches in the ext4.git tree Sedat Dilek
2016-03-27 18:15 ` Theodore Ts'o
2016-03-27 19:31 ` Sedat Dilek
2016-03-28 12:36 ` Theodore Ts'o [this message]
2016-03-27 22:51 ` Sedat Dilek
2016-03-28 14:02 ` Chris Mason
2016-03-29 17:15 ` Theodore Ts'o
2016-03-29 20:12 ` Chris Mason
2016-03-29 19:58 ` Al Viro
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=20160328123616.GA3321@thunk.org \
--to=tytso@mit.edu \
--cc=dhowells@redhat.com \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--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).