From: Jens Axboe <axboe@fb.com>
To: <torvalds@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Two fixes for 4.0-rc2
Date: Fri, 27 Feb 2015 08:42:48 -0700 [thread overview]
Message-ID: <20150227154248.GA12546@kernel.dk> (raw)
Hi Linus,
Two smaller fixes for this cycle:
- A fixup from Keith so that NVMe compiles without BLK_INTEGRITY,
basically just moving the code around appropriately.
- A fixup for shm, fixing an oops in shmem_mapping() for mapping with no
inode. From Sasha.
Please pull!
git://git.kernel.dk/linux-block.git for-linus
for you to fetch changes up to f0774d884bad7007b54cfffb5c93c23420c75aa6:
mm: shmem: check for mapping owner before dereferencing (2015-02-23 10:00:11 -0800)
----------------------------------------------------------------
Keith Busch (1):
NVMe: Fix for BLK_DEV_INTEGRITY not set
Sasha Levin (1):
mm: shmem: check for mapping owner before dereferencing
drivers/block/nvme-core.c | 99 +++++++++++++++++++++++++++--------------------
mm/shmem.c | 3 ++
2 files changed, 61 insertions(+), 41 deletions(-)
--
Jens Axboe
reply other threads:[~2015-02-27 15:43 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=20150227154248.GA12546@kernel.dk \
--to=axboe@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linuxfoundation.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