From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Dan Carpenter
<dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
"Hefty,
Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma
(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: smatch warnings on the IB core
Date: Sun, 27 Oct 2013 08:45:25 +0200 [thread overview]
Message-ID: <526CB685.40607@mellanox.com> (raw)
Hi Dan,
With the latest smatch I still see these hits on the IB core, basically,
I would be happy to see the IB stack free from such warnings and then we
can easily require each new patch not to introduce them... can you shed
some light on the problem and possible solutions?
> drivers/infiniband/core/user_mad.c:912 ib_umad_sm_open() warn:
> inconsistent returns sem:&port->sm_sem: locked (908) unlocked (886
> [(-6)], 912 [s32min-(-1),1-s32max], 912 [(-512)], 912 [(-11)])
>
> drivers/infiniband/core/cma.c:1336 cma_req_handler() warn:
> inconsistent returns mutex:&listen_id->handler_mutex: locked (1271
> [(-22)], 1274 [(-103)]) unlocked (1323 [0], 1336
> [s32min-(-1),1-s32max], 1336 [(-12)])
>
> drivers/infiniband/core/cma.c:1535 iw_conn_req_handler() warn:
> inconsistent returns mutex:&listen_id->handler_mutex: locked (1463
> [(-103)]) unlocked (1535 [0], 1535 [s32min-(-1),1-s32max], 1535
> [s32min-(-1),1-s32max], 1535 [s32min-(-1),1-s32max], 1535
> [s32min-(-1),1-s32max], 1535 [(-12)])
Sean, if you want to reproduce clone git://repo.or.cz/smatch.git and use
this command
$ make C=2 CHECK="/patch/to/smatch/smatch_scripts/../smatch
--project=kernel" drivers/infiniband/core/ -j 12
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2013-10-27 6:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 6:45 Or Gerlitz [this message]
[not found] ` <526CB685.40607-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-28 16:32 ` smatch warnings on the IB core Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237388CF16CC-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-10-29 7:03 ` Or Gerlitz
2013-10-29 7:53 ` Dan Carpenter
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=526CB685.40607@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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