From: Viacheslav Dubeyko <firstname.lastname@example.org>
To: "Ernesto A. Fernández" <email@example.com>
Cc: Andrew Morton <firstname.lastname@example.org>,
email@example.com, "Xu, Wen" <firstname.lastname@example.org>
Subject: Re: [PATCH] hfsplus: fix NULL dereference in hfsplus_lookup()
Date: Wed, 22 Aug 2018 13:18:39 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
On Wed, 2018-08-22 at 15:46 -0300, Ernesto A. Fernández wrote:
> On Tue, Aug 21, 2018 at 04:05:25PM -0700, Andrew Morton wrote:
> > On Thu, 12 Jul 2018 15:55:33 -0700 Viacheslav Dubeyko <firstname.lastname@example.org> wrote:
> > > On Thu, 2018-07-12 at 18:53 -0300, Ernesto A. Fernández wrote:
> > > > Check that the hidden directory is not NULL before using it, instead of
> > > > after.
> > > >
> > > > Reported-by: Wen Xu <email@example.com>
> > > > Signed-off-by: Ernesto A. Fernández <firstname.lastname@example.org>
> > > > ---
> > >
> > > It's really hard to understand this simple patch. I believe it makes
> > > sense to rework the patch slightly with the goal to make it more clear.
> > > Also, it will be great to add a short comment in the code to explain
> > > what's wrong.
> I don't think it's reasonable to expect a comment explaining why we can't
> dereference NULL.
The good comment is always really important part of the patch.
> > > I think it makes sense to split this long check condition on something
> > > more clear, simple and elegant.
> The long check condition may not be ideal, but there's a lot of code in
> the module that could use style improvements. I don't think that should be
> a priority right now, with plenty of serious bugs left to fix.
Bad style of code is one of the reason of bugs. If you don't try to
improve the code then you can simply create an another serious bug and
nobody will be able to understand your fix. The bad style of code in the
module is not the excuse at all. It's the way of open-source community
to achieve the good style of code by means of the discussion. Moreover,
the goal of bug fix is the improvement of code style too but not only to
resolve the issue. Another guys need to understand your way of the fix
> > No response, causing this patch to be stuck in limbo land?
> I believe I sent a second version of this patch.
next prev parent reply other threads:[~2018-08-22 23:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 21:53 [PATCH] hfsplus: fix NULL dereference in hfsplus_lookup() Ernesto A. Fernández
2018-07-12 22:55 ` Viacheslav Dubeyko
2018-08-21 23:05 ` Andrew Morton
2018-08-22 18:46 ` Ernesto A. Fernández
2018-08-22 20:18 ` Viacheslav Dubeyko [this message]
2018-08-22 21:38 ` Ernesto A. Fernández
[not found] ` <email@example.com>
2018-07-12 23:07 ` Ernesto A. Fernández
[not found] ` <firstname.lastname@example.org>
2018-07-12 23:23 ` Ernesto A. Fernández
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).