Linux filesystem development
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux FS Dev Mailing List <linux-fsdevel@vger.kernel.org>,
	Linux F2FS Dev Mailing List
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: [GIT PULL] f2fs and fscrypto bug fixes for 4.6-rc4
Date: Thu, 14 Apr 2016 13:50:07 -0700	[thread overview]
Message-ID: <20160414205007.GA28828@jaegeuk.gateway> (raw)

Hi Linus,

Could you please pull these patches which were missing in -rc3?
In addition to f2fs/fscrypto fixes, I've added one patch which prevents RCU
mode lookup in d_revalidate, as Al mentioned.

Thanks,

The following changes since commit bf16200689118d19de1b8d2a3c314fc21f5dc7bb:

  Linux 4.6-rc3 (2016-04-10 17:58:30 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/for-linus-4.6-rc4

for you to fetch changes up to 03a8bb0e53d9562276045bdfcf2b5de2e4cff5a1:

  ext4/fscrypto: avoid RCU lookup in d_revalidate (2016-04-12 20:01:35 -0700)

----------------------------------------------------------------
for-linus-4.6-rc4

These patches fix f2fs and fscrypto based on -rc3 bug fixes in ext4 crypto,
which have not yet been fully propagated as follows.
 - use of dget_parent and file_dentry to avoid crashes
 - disallow RCU-mode lookup in d_invalidate
 - disallow -ENOMEM in the core data encryption path

----------------------------------------------------------------
Jaegeuk Kim (4):
      fscrypto: use dget_parent() in fscrypt_d_revalidate()
      f2fs: use dget_parent and file_dentry in f2fs_file_open
      fscrypto: don't let data integrity writebacks fail with ENOMEM
      ext4/fscrypto: avoid RCU lookup in d_revalidate

 fs/crypto/crypto.c       | 51 ++++++++++++++++++++++++++++++------------------
 fs/ext4/crypto.c         |  4 ++++
 fs/f2fs/data.c           | 16 ++++++++++++---
 fs/f2fs/file.c           | 10 +++++++---
 include/linux/fscrypto.h |  9 +++++----
 5 files changed, 61 insertions(+), 29 deletions(-)

                 reply	other threads:[~2016-04-14 20:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160414205007.GA28828@jaegeuk.gateway \
    --to=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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