From: kbuild test robot <lkp@intel.com>
To: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org, dvyukov@google.com,
nhorman@tuxdriver.com, vyasevich@gmail.com,
linux-sctp@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller@googlegroups.com, kcc@google.com, glider@google.com,
sasha.levin@oracle.com, edumazet@google.com, davem@davemloft.net
Subject: Re: [PATCH net] sctp: fix copying more bytes than expected in sctp_add_bind_addr
Date: Tue, 8 Mar 2016 07:17:55 +0800 [thread overview]
Message-ID: <201603080758.oSIf1B2b%fengguang.wu@intel.com> (raw)
In-Reply-To: <6cddeac76bb79521e58f9bbba653db774191eb1c.1457382433.git.marcelo.leitner@gmail.com>
Hi Marcelo,
[auto build test WARNING on net/master]
url: https://github.com/0day-ci/linux/commits/Marcelo-Ricardo-Leitner/sctp-fix-copying-more-bytes-than-expected-in-sctp_add_bind_addr/20160308-052009
coccinelle warnings: (new ones prefixed by >>)
>> net/sctp/bind_addr.c:458:42-48: ERROR: application of sizeof to pointer
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next parent reply other threads:[~2016-03-07 23:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 23:17 kbuild test robot [this message]
2016-03-07 21:17 ` Marcelo Ricardo Leitner
2016-03-07 23:17 ` [PATCH] sctp: fix noderef.cocci warnings kbuild test robot
2016-03-07 23:27 ` [PATCH net] sctp: fix copying more bytes than expected in sctp_add_bind_addr Marcelo Ricardo Leitner
2016-03-08 4:15 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2016-01-25 17:29 net/sctp: out-of-bounds access " Neil Horman
2016-01-25 17:52 ` [PATCH net] sctp: fix copying more bytes than expected " Marcelo Ricardo Leitner
2016-01-26 13:28 ` Dmitry Vyukov
2016-03-07 19:44 ` Marcelo Ricardo Leitner
2016-03-07 19:45 ` Dmitry Vyukov
2016-03-07 19:51 ` Marcelo Ricardo Leitner
2016-03-07 19:56 ` Dmitry Vyukov
2016-03-07 20:00 ` Marcelo Ricardo Leitner
2016-03-07 20:21 ` David Miller
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=201603080758.oSIf1B2b%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=glider@google.com \
--cc=kbuild-all@01.org \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@googlegroups.com \
--cc=vyasevich@gmail.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
all inboxes | Powered by JetHome®