From: Dan Carpenter <dan.carpenter@oracle.com>
To: amir73il@gmail.com
Cc: linux-unionfs@vger.kernel.org
Subject: [bug report] ovl: detect overlapping layers
Date: Wed, 29 May 2019 13:31:20 +0300 [thread overview]
Message-ID: <20190529103120.GA15021@mwanda> (raw)
Hello Amir Goldstein,
The patch 0e7f2cccb42a: "ovl: detect overlapping layers" from Apr 18,
2019, leads to the following static checker warning:
fs/overlayfs/super.c:998 ovl_setup_trap()
warn: passing a valid pointer to 'PTR_ERR'
fs/overlayfs/super.c
991 static int ovl_setup_trap(struct super_block *sb, struct dentry *dir,
992 struct inode **ptrap, const char *name)
993 {
994 struct inode *trap;
995 int err;
996
997 trap = ovl_get_trap_inode(sb, dir);
998 err = PTR_ERR(trap);
999 if (IS_ERR(trap) && err == -ELOOP) {
1000 pr_err("overlayfs: conflicting %s path\n", name);
1001 return err;
1002 }
1003
1004 *ptrap = trap;
1005 return 0;
1006 }
The warning message is wrong but the code is also wrong. The
ovl_get_trap_inode() can return ERR_PTR(-ENOMEM) and that would lead to
and Oops when we try to call iput() on it.
regards,
dan carpenter
next reply other threads:[~2019-05-29 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 10:31 Dan Carpenter [this message]
2019-05-29 10:42 ` [bug report] ovl: detect overlapping layers Amir Goldstein
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=20190529103120.GA15021@mwanda \
--to=dan.carpenter@oracle.com \
--cc=amir73il@gmail.com \
--cc=linux-unionfs@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