From: Boaz Harrosh <bharrosh@panasas.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
open-osd <osd-dev@open-osd.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: [GIT PULL] exofs: 3 changes to exofs & osd
Date: Mon, 17 Dec 2012 18:53:21 +0200 [thread overview]
Message-ID: <50CF4E01.5030004@panasas.com> (raw)
Hi Linus.
Please pull the following changes since commit [ddffeb8c] Linux 3.7-rc1
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
[861d6660] exofs: don't leak io_state and pages on read error (2012-12-14 12:17:32 +0200)
These are just 3 patches, the last two are bug fixes on the error paths
in exofs.
The important patch is the one to osd_uld which adds sysfs info to osd
devices for use by user-mode clustering discovery software. I'm already
sitting on this patch since before February this year, It is important for
some of the big installation cluster systems, who's been compiling their
own kernel just for that patch.
Thanks in advance
Boaz
----------------------------------------------------------------
Boaz Harrosh (1):
exofs: don't leak io_state and pages on read error
Idan Kedar (1):
exofs: clean up the correct page collection on write error
Sachin Bhamare (1):
osduld: Add osdname & systemid sysfs at scsi_osd class
drivers/scsi/osd/osd_uld.c | 28 ++++++++++++++++++++++++++++
fs/exofs/inode.c | 16 +++++++++-------
2 files changed, 37 insertions(+), 7 deletions(-)
next reply other threads:[~2012-12-17 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 16:53 Boaz Harrosh [this message]
2012-12-18 10:58 ` [GIT PULL] exofs: 3 changes to exofs & osd James Bottomley
2012-12-18 11:18 ` Boaz Harrosh
2012-12-18 11:28 ` James Bottomley
2012-12-18 11:35 ` 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=50CF4E01.5030004@panasas.com \
--to=bharrosh@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@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 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).