From: Fabian Frederick <fabf@skynet.be>
To: akpm@linux-foundation.org
Cc: jaharkes@cs.cmu.edu, coda@cs.cmu.edu,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
fabf@skynet.be
Subject: [PATCH 6/7 linux-next] coda: remove sb test in coda_fid_to_inode()
Date: Fri, 19 Oct 2018 10:19:32 +0200 [thread overview]
Message-ID: <1539937173-26260-7-git-send-email-fabf@skynet.be> (raw)
In-Reply-To: <1539937173-26260-1-git-send-email-fabf@skynet.be>
coda_fid_to_inode() is only called by coda_downcall() where
sb is already being tested.
Signed-off-by: Fabian Frederick <fabf@skynet.be>
---
fs/coda/cnode.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/fs/coda/cnode.c b/fs/coda/cnode.c
index 845b5a6..c42d340 100644
--- a/fs/coda/cnode.c
+++ b/fs/coda/cnode.c
@@ -137,11 +137,6 @@ struct inode *coda_fid_to_inode(struct CodaFid *fid, struct super_block *sb)
struct inode *inode;
unsigned long hash = coda_f2i(fid);
- if ( !sb ) {
- pr_warn("%s: no sb!\n", __func__);
- return NULL;
- }
-
inode = ilookup5(sb, hash, coda_test_inode, fid);
if ( !inode )
return NULL;
--
2.4.11
next prev parent reply other threads:[~2018-10-19 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 8:19 [PATCH 0/7 linux-next] coda: fs clean-up Fabian Frederick
2018-10-19 8:19 ` [PATCH 1/7 linux-next] coda: remove CODA_FREE Fabian Frederick
2018-10-19 8:19 ` [PATCH 2/7 linux-next] coda: destroy mutex in put_super() Fabian Frederick
2018-10-19 8:19 ` [PATCH 3/7 linux-next] coda: use SIZE() for stat Fabian Frederick
2018-10-19 8:19 ` [PATCH 4/7 linux-next] coda: add __init to init_coda_psdev() Fabian Frederick
2018-10-19 8:19 ` [PATCH 5/7 linux-next] coda: remove sysctl object from module when unused Fabian Frederick
2018-10-19 8:19 ` Fabian Frederick [this message]
2018-10-19 8:19 ` [PATCH 7/7 linux-next] coda: ftoc validity check integration Fabian Frederick
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=1539937173-26260-7-git-send-email-fabf@skynet.be \
--to=fabf@skynet.be \
--cc=akpm@linux-foundation.org \
--cc=coda@cs.cmu.edu \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).