From: Dan Carpenter <dan.carpenter@oracle.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: kernel-janitors@vger.kernel.org, linux-raid@vger.kernel.org,
dm-devel@redhat.com, Shaohua Li <shli@kernel.org>,
Milan Broz <gmazyland@gmail.com>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: dm crypt: remove an impossible condition
Date: Sat, 18 Mar 2017 07:14:22 +0300 [thread overview]
Message-ID: <20170318041422.GC4102@mwanda> (raw)
In-Reply-To: <20170317213819.GC6475@redhat.com>
On Fri, Mar 17, 2017 at 05:38:19PM -0400, Mike Snitzer wrote:
> On Fri, Mar 17 2017 at 4:46pm -0400,
> Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> > Static checkers complain that it doesn't make sense to check if "sval"
> > is NULL. The intention was to check if strchr() returned NULL, but in
> > that situation "sval" would be "NULL + 1" so the check doesn't work. We
> > know from the sscanf() that there is a ':' character in the string so
> > the check is unnecessary and can be removed.
> >
> > Now that the check doesn't depend on "sval" it can be moved earlier
> > for readability.
> >
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> Thanks Dan, I've folded this fix into the original commit, see:
> https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-4.12&id=cf22cd5f3afe7335afee5659f7450000e8fa2a15
>
> I didn't add your Signed-off-by though, I can backfill that if you
> like.. it is just I didn't want to taint you with all the extensive
> changes in that commit.
That's fine, thanks. Sign-off isn't really the appropriate tag anyway...
regards,
dan carpenter
prev parent reply other threads:[~2017-03-18 4:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 20:46 [PATCH] dm crypt: remove an impossible condition Dan Carpenter
2017-03-17 21:38 ` Mike Snitzer
2017-03-18 4:14 ` Dan Carpenter [this message]
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=20170318041422.GC4102@mwanda \
--to=dan.carpenter@oracle.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@kernel.org \
--cc=snitzer@redhat.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;
as well as URLs for NNTP newsgroup(s).