From: LABBE Corentin <clabbe.montjoie@gmail.com>
To: acme@ghostprotocols.net, al.drozdov@gmail.com,
alexander.h.duyck@redhat.com, daniel@iogearbox.net,
davem@davemloft.net, dmitry.tarnyagin@lockless.no,
dwmw2@infradead.org, edumazet@google.com, eyal.birger@gmail.com,
fw@strlen.de, gustavo@padovan.org, hannes@stressinduktion.org,
herbert@gondor.apana.org.au, jiri@resnulli.us, jmorris@namei.org,
johan.hedberg@gmail.com, kaber@trash.net, kuznet@ms2.inr.ac.ru,
marcel@holtmann.org, mst@redhat.com, pablo@netfilter.org,
samuel@sortiz.org, tom@herbertland.com, viro@zeniv.linux.org.uk,
willemb@google.com, yoshfuji@linux-ipv6.org
Cc: linux-bluetooth@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: (unknown)
Subject:
Date: Fri, 23 Oct 2015 14:10:25 +0200 [thread overview]
Message-ID: <1445602236-24130-1-git-send-email-clabbe.montjoie@gmail.com> (raw)
Hello
This patch series was begun by my finding that memcpy_[to|from]_msg have
a parameter len which is an int but used as size_t in whole functions.
Without blindly changing the parameter to size_t, I have tried to see if
anywhere in linux source code, someone give a negative argument with
the following (unfinished) coccinnelle patch.
virtual report
@@
type T;
signed T i;
@@
(
memcpy_from_msg
|
memcpy_to_msg
)
(...,
- i)
+ (size_t)i)
With that I found many place where int variable is used to store unsigned values
and which could be set as size_t since there are used againt size_t
and/or given to functions that wait for size_t.
It permit also to found a bug in net/llc/af_llc.c where a size_t variable
stored error codes.
Regards
next reply other threads:[~2015-10-23 12:11 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 12:10 LABBE Corentin [this message]
2015-10-23 12:10 ` [PATCH 11/11] crypto: algif: Change some variable to size_t LABBE Corentin
2015-11-17 14:08 ` Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2017-10-20 8:42 (unknown), membership
2017-10-17 0:33 (unknown), membership
2017-10-06 8:31 (unknown), smallgroups
2017-10-04 15:33 (unknown), membership
2017-09-22 3:39 (unknown), service
2017-09-02 0:58 (unknown), smallgroups
2017-09-01 11:40 (unknown), witt.kohl
2017-08-31 4:52 (unknown), archerrp
2017-08-25 0:32 (unknown), agiva
2017-08-11 6:14 (unknown), администратор
2017-08-09 10:20 (unknown), системы администратор
2017-08-02 3:45 (unknown), системы администратор
2017-07-13 4:49 (unknown), delaware.orders
2017-07-10 21:53 (unknown), agiva
2017-07-10 3:45 (unknown), системы администратор
2017-07-09 13:02 (unknown), smallgroups
2017-07-05 6:55 (unknown), agiva
2017-06-28 3:56 (unknown), системы администратор
2017-06-25 5:14 (unknown), archerrp
2017-06-24 15:03 (unknown), archerrp
2017-06-23 12:26 (unknown), archerrp
2017-06-18 13:58 (unknown), membership
2017-06-13 21:38 (unknown), douille.l
2017-06-11 0:20 (unknown), service
2017-06-10 5:29 (unknown), agiva
2017-06-08 14:09 (unknown), service
2017-06-04 19:55 (unknown), archerrp
2017-06-01 1:55 (unknown), cdevries
2017-05-23 16:24 (unknown), agiva
2017-05-23 8:42 (unknown), delaware.orders
2017-05-21 8:55 (unknown), agiva
2017-05-19 4:32 (unknown), archerrp
2017-05-18 14:13 (unknown), agiva
2017-04-28 8:36 (unknown), администратор
2017-04-21 17:06 (unknown), Mr.Jerry Smith
2017-04-21 9:25 (unknown), delaware.orders
2017-04-15 13:53 (unknown), smallgroups
2017-04-10 5:46 (unknown), archerrp
2017-04-06 13:43 (unknown), agiva
2017-01-19 4:56 (unknown), archerrp
2017-01-13 11:28 (unknown), service
2017-01-03 6:57 (unknown), системы администратор
2017-01-03 6:48 (unknown), системы администратор
2017-01-03 6:48 (unknown), системы администратор
2016-12-18 10:35 (unknown), linux-crypto
2016-12-16 10:46 (unknown), системы администратор
2016-12-14 18:22 (unknown), witt.kohl
2016-08-30 15:53 (unknown), Iaroslav Gridin
2016-06-01 4:21 (unknown), Jeffrey Walton
2016-05-15 3:15 (unknown), membership
2016-04-08 2:06 (unknown) contact
2015-09-23 10:48 (unknown), jerryfunds247777
2015-08-30 1:57 (unknown), jerryfunds3
2015-08-29 18:29 (unknown), jerryfunds20
2015-07-01 11:53 (unknown), Sasnett_Karen
2012-05-25 13:45 (unknown), robothroli company
2012-05-05 18:59 (unknown), Mrs Sabah Halif
2012-02-15 17:47 (unknown), Ann Adams
2011-05-21 12:54 (unknown), western101@algish.com
2010-09-06 13:34 (unknown), Jan Chadima
2010-09-05 0:36 (unknown), Tobias Karnat
2009-07-27 16:23 (unknown) vivianofferplc013
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=1445602236-24130-1-git-send-email-clabbe.montjoie@gmail.com \
--to=clabbe.montjoie@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=al.drozdov@gmail.com \
--cc=alexander.h.duyck@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dmitry.tarnyagin@lockless.no \
--cc=dwmw2@infradead.org \
--cc=edumazet@google.com \
--cc=eyal.birger@gmail.com \
--cc=fw@strlen.de \
--cc=gustavo@padovan.org \
--cc=hannes@stressinduktion.org \
--cc=herbert@gondor.apana.org.au \
--cc=jiri@resnulli.us \
--cc=jmorris@namei.org \
--cc=johan.hedberg@gmail.com \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=samuel@sortiz.org \
--cc=tom@herbertland.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willemb@google.com \
--cc=yoshfuji@linux-ipv6.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 NNTP newsgroup(s).