From: Thomas Gleixner <tglx@linutronix.de>
To: Nick Krause <xerofoify@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
akpm@linux-foundation.org, viro@zeniv.linux.org.uk,
fabf@skynet.be, kirill.shutemov@linux.intel.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Check for Null return of function of affs_bread in function affs_truncate
Date: Sat, 21 Jun 2014 01:59:15 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1406210143030.5170@nanos> (raw)
In-Reply-To: <CAPDOMVgwT2=iWAHOhgHSBY1B+KoWHQgCdK4idD2miwB=_eMs5Q@mail.gmail.com>
On Fri, 20 Jun 2014, Nick Krause wrote:
> Ok that's fine I would return as if it's a NULL the other parts of the
> function can't continue.
> Nick
>
> On Thu, Jun 19, 2014 at 1:21 AM, Dan Carpenter <dan.carpenter@oracle.com> wrote:
> > On Wed, Jun 18, 2014 at 06:08:05PM -0400, Nicholas Krause wrote:
> >> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> >> ---
> >> fs/affs/file.c | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/fs/affs/file.c b/fs/affs/file.c
> >> index a7fe57d..f26482d 100644
> >> --- a/fs/affs/file.c
> >> +++ b/fs/affs/file.c
> >> @@ -923,6 +923,8 @@ affs_truncate(struct inode *inode)
> >>
> >> while (ext_key) {
> >> ext_bh = affs_bread(sb, ext_key);
> >> + if (!ext_bh)
> >> + return;
> >
> > The problem is that we don't know if we should return here or break
> > here. If you don't understand the code, then it's best to just leave it
> > alone.
Dan, what kind of attitude is that?
Nick certainly found an issue where a possible NULL return from
affs_bread() can cause havoc.
Do YOU understand that code?
If yes, you better explain, WHY Nicks finding is a false positive
instead of just telling him off in a very inpolite way.
If not, you better refrain from telling a reporter that he does not
understand the code and should stay away.
You clearly stated that you do not understand it either:
> > The problem is that we don't know if we should return here or break
> > here.
The problem here is that proceeding with a known NULL pointer is wrong
to begin with. It does not matter at all whether break or return is
the proper thing to do. What matters is that proceeding with a NULL
pointer is wrong to begin with, no matter what.
So either explain why this is a non issue and the NULL pointer return
cannot happen or shut up and try to find a proper solution for that
"return" vs. "break" issue.
Thanks,
tglx
next prev parent reply other threads:[~2014-06-20 23:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 22:08 Nicholas Krause
2014-06-19 5:21 ` Dan Carpenter
2014-06-20 16:30 ` Nick Krause
2014-06-20 23:59 ` Thomas Gleixner [this message]
2014-06-21 2:25 ` Nick Krause
2014-06-21 2:38 ` Andrew Morton
2014-06-21 2:55 ` Nick Krause
2014-06-21 3:09 ` Andrew Morton
2014-06-21 3:20 ` Nick Krause
2014-06-22 19:12 ` Al Viro
2014-07-11 15:05 ` Dan Carpenter
2014-07-13 6:18 ` Nick Krause
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.DEB.2.10.1406210143030.5170@nanos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=fabf@skynet.be \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=xerofoify@gmail.com \
/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
all inboxes | Powered by JetHome®