From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Mats Kärrman" <Mats.Karrman@tritech.se>
Cc: Alexander Stein <alexanders83@web.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] UBI: Fix potential NULL-pointer dereference
Date: Mon, 31 Mar 2014 12:46:40 +0300 [thread overview]
Message-ID: <1396259200.9016.59.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <ED3E0BCACD909541BA94A34C4A164D4C5B3A869F@post.tritech.se>
On Mon, 2014-03-31 at 06:18 +0000, Mats Kärrman wrote:
> On Friday, March 28, 2014 10:04 PM, Alexander Stein wrote:
> >
> > It's no use to debug print a string before checking on NULL.
> >
>
> If the string is NULL, that could be very useful to know when debugging and
> the print function should handle that gracefully, i.e. by not printing anything
> for %s.
%s will just result in (null), I do not see any issue with this.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2014-03-31 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 21:04 [PATCH] UBI: Fix potential NULL-pointer dereference Alexander Stein
2014-03-31 6:18 ` Mats Kärrman
2014-03-31 9:46 ` Artem Bityutskiy [this message]
2014-03-31 17:00 ` Alexander Stein
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=1396259200.9016.59.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=Mats.Karrman@tritech.se \
--cc=alexanders83@web.de \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.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