From: Dan Carpenter <dan.carpenter@oracle.com>
To: smatch@vger.kernel.org
Subject: passing zero to PTR_ERR() warnings
Date: Thu, 9 May 2019 16:51:18 +0300 [thread overview]
Message-ID: <20190509135118.GD21059@kadam> (raw)
Everyone seems to be hitting this warning, but I can't reproduce it at
all. It came from a bug when I made pointers unsigned...
I though I fixed it in commit 8a9817501654 ("zero_to_err_ptr: fix fall
out from unsigned pointer changes and improve") but now I can't
reproduce it even when I revert that patch.
I'm using a clean smatch clone and a clean kernel clone, but I just
can't trigger false positives. I get valid warnings still but not the
false positives.
Can anyone help me figure this out?
regards,
dan carpenter
reply other threads:[~2019-05-09 13:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190509135118.GD21059@kadam \
--to=dan.carpenter@oracle.com \
--cc=smatch@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).