From: Boaz Harrosh <bharrosh@panasas.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
NFS list <linux-nfs@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [git pull] Few fixes to ORE and EXOFS
Date: Mon, 27 Jan 2014 22:26:32 +0200 [thread overview]
Message-ID: <52E6C0F8.3030002@panasas.com> (raw)
Dear Linus
Please pull the following changes since v3.12 commit [5e01dc7b]:
They are available in the git repository at:
git://git.open-osd.org/linux-open-osd.git for-linus
for you to fetch changes up to 19350e7627a6f3b0f662cbd2eb1128c9961a41fe:
exofs: Print less in r4w (2014-01-23 18:54:14 +0200)
The main fix here, the first patch, is also destined for Stable@. The rest
is small trivia and cosmetics. The ORE patches effect both exofs and pnfs-objects
very reproducible bugs.
----------------------------------------------------------------
Boaz Harrosh (5):
ore: Fix wrong math in allocation of per device BIO
ore: Don't crash on NULL bio in _clear_bio
exofs: Allow O_DIRECT open
exofs: Allow corrupted directory entry to be empty file
exofs: Print less in r4w
fs/exofs/inode.c | 31 +++++++++++++++++++------------
fs/exofs/ore.c | 45 +++++++++++++++++++++++++++++++--------------
include/scsi/osd_ore.h | 1 +
3 files changed, 51 insertions(+), 26 deletions(-)
Thanks
Boaz
WARNING: multiple messages have this Message-ID (diff)
From: Boaz Harrosh <bharrosh-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
To: Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
NFS list <linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
open-osd <osd-dev-yNzVSZO3znNg9hUCZPvPmw@public.gmane.org>,
linux-fsdevel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [git pull] Few fixes to ORE and EXOFS
Date: Mon, 27 Jan 2014 22:26:32 +0200 [thread overview]
Message-ID: <52E6C0F8.3030002@panasas.com> (raw)
Dear Linus
Please pull the following changes since v3.12 commit [5e01dc7b]:
They are available in the git repository at:
git://git.open-osd.org/linux-open-osd.git for-linus
for you to fetch changes up to 19350e7627a6f3b0f662cbd2eb1128c9961a41fe:
exofs: Print less in r4w (2014-01-23 18:54:14 +0200)
The main fix here, the first patch, is also destined for Stable@. The rest
is small trivia and cosmetics. The ORE patches effect both exofs and pnfs-objects
very reproducible bugs.
----------------------------------------------------------------
Boaz Harrosh (5):
ore: Fix wrong math in allocation of per device BIO
ore: Don't crash on NULL bio in _clear_bio
exofs: Allow O_DIRECT open
exofs: Allow corrupted directory entry to be empty file
exofs: Print less in r4w
fs/exofs/inode.c | 31 +++++++++++++++++++------------
fs/exofs/ore.c | 45 +++++++++++++++++++++++++++++++--------------
include/scsi/osd_ore.h | 1 +
3 files changed, 51 insertions(+), 26 deletions(-)
Thanks
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-01-27 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 20:26 Boaz Harrosh [this message]
2014-01-27 20:26 ` [git pull] Few fixes to ORE and EXOFS Boaz Harrosh
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=52E6C0F8.3030002@panasas.com \
--to=bharrosh@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=osd-dev@open-osd.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 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.