From: Mike Marshall <hubcap@omnibond.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Mike Marshall <hubcap@omnibond.com>
Subject: [GIT PULL] orangefs: fixes and a cleanup
Date: Tue, 23 Oct 2018 12:16:01 -0400 [thread overview]
Message-ID: <CAOg9mSRFWALOeLAZUeBNdCoK0rysy7qraV7uEBeBGo46f0UjpQ@mail.gmail.com> (raw)
Hi Linus...
I'm sending this a second time, I left my gmail in html mode the
first time and fs-devel bounced it... sorry for the trouble...
The following changes since commit 0238df646e6224016a45505d2c111a24669ebe21:
Linux 4.19-rc7 (2018-10-07 17:26:02 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux.git
tags/for-linus-4.20-ofs1
for you to fetch changes up to 22fc9db296fcf7ac30151c52765a7fba10870ab7:
orangefs: no need to check for service_operation returns > 0
(2018-10-18 14:05:46 -0400)
----------------------------------------------------------------
orangefs: fixes and a cleanup
fixes:
+ fix superfluous service_operation return code check in orangefs_lookup
+ fix some error code paths that missed kmem_cache_free
+ don't let orangefs_iget return NULL
+ don't let orangefs_new_inode return NULL
+ cache NULL when both default_acl and acl are NULL
cleanup:
+ rate limit the client not running info message
----------------------------------------------------------------
Chengguang Xu (1):
orangefs: cache NULL when both default_acl and acl are NULL
Colin Ian King (1):
orangefs: rate limit the client not running info message
Mike Marshall (4):
orangefs: don't let orangefs_new_inode return NULL
orangefs: don't let orangefs_iget return NULL.
orangefs: some error code paths missed kmem_cache_free
orangefs: no need to check for service_operation returns > 0
fs/orangefs/acl.c | 4 ++++
fs/orangefs/inode.c | 8 ++++++--
fs/orangefs/namei.c | 8 ++++----
fs/orangefs/orangefs-sysfs.c | 2 +-
4 files changed, 15 insertions(+), 7 deletions(-)
next reply other threads:[~2018-10-24 0:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 16:16 Mike Marshall [this message]
[not found] <CAOg9mST1mcs7ceB2hcLQe1UzWXk9UWXw7ZGafrCze5C9REMRjA@mail.gmail.com>
2018-10-24 16:29 ` [GIT PULL] orangefs: fixes and a cleanup Linus Torvalds
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=CAOg9mSRFWALOeLAZUeBNdCoK0rysy7qraV7uEBeBGo46f0UjpQ@mail.gmail.com \
--to=hubcap@omnibond.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).