From: Martin Brandenburg <martin@omnibond.com>
To: torvalds@linux-foundation.org
Cc: viro@zeniv.linux.org.uk, hubcap@omnibond.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] orangefs bugfixes for rc2
Date: Thu, 31 Mar 2016 12:17:23 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSO.2.20.1603311208110.15868@server1.sysblue.org> (raw)
Linus,
Please pull two bugfixes for OrangeFS.
One fixes a rather serious reference counting bug and one fixes a typo
which would stop the latest stable userspace client from starting up.
Thanks,
-- Martin
The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
are available in the git repository at:
https://github.com/martinbrandenburg/linux.git for-linus
for you to fetch changes up to 878dfd3210e0bfc047995022de3091724ea9a5f6:
orangefs: minimum userspace version is 2.9.3 (2016-03-31 12:06:00 -0400)
----------------------------------------------------------------
Martin Brandenburg (2):
orangefs: don't put readdir slot twice
orangefs: minimum userspace version is 2.9.3
fs/orangefs/dir.c | 8 +++-----
fs/orangefs/protocol.h | 2 +-
2 files changed, 4 insertions(+), 6 deletions(-)
next reply other threads:[~2016-03-31 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 16:17 Martin Brandenburg [this message]
2016-03-31 19:27 ` [git pull] orangefs bugfixes for rc2 Linus Torvalds
2016-03-31 21:01 ` Mike Marshall
2016-03-31 21:06 ` Mike Marshall
2016-03-31 22:11 ` Linus Torvalds
2016-03-31 22:59 ` Al Viro
2016-04-01 1:19 ` Theodore Ts'o
2016-04-01 19:49 ` Martin Brandenburg
2016-04-01 22:35 ` Linus Torvalds
2016-04-01 23:29 ` Mike Marshall
2016-04-01 23:23 ` Joe Perches
2016-04-02 1:32 ` Martin Brandenburg
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=alpine.BSO.2.20.1603311208110.15868@server1.sysblue.org \
--to=martin@omnibond.com \
--cc=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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).