From: Ying Xue <ying.xue@windriver.com>
To: <netdev@vger.kernel.org>
Cc: syzkaller-bugs@googlegroups.com, tipc-discussion@lists.sourceforge.net
Subject: [net 0/6] tipc: fix uninit-value issues reported by syzbot
Date: Mon, 14 Jan 2019 17:22:23 +0800 [thread overview]
Message-ID: <1547457749-24831-1-git-send-email-ying.xue@windriver.com> (raw)
Recently, syzbot complained that TIPC module exits several issues
associated with uninit-value type. So, in this series, we try to
fix them as many as possible.
Ying Xue (6):
tipc: fix uninit-value in in tipc_conn_rcv_sub
tipc: fix uninit-value in tipc_nl_compat_link_reset_stats
tipc: fix uninit-value in tipc_nl_compat_bearer_enable
tipc: fix uninit-value in tipc_nl_compat_link_set
tipc: fix uninit-value in tipc_nl_compat_name_table_dump
tipc: fix uninit-value in tipc_nl_compat_doit
net/tipc/netlink_compat.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++-
net/tipc/topsrv.c | 2 +-
2 files changed, 50 insertions(+), 2 deletions(-)
--
2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Ying Xue <ying.xue@windriver.com>
To: <netdev@vger.kernel.org>
Cc: <jon.maloy@ericsson.com>, <tipc-discussion@lists.sourceforge.net>,
<syzkaller-bugs@googlegroups.com>
Subject: [net 0/6] tipc: fix uninit-value issues reported by syzbot
Date: Mon, 14 Jan 2019 17:22:23 +0800 [thread overview]
Message-ID: <1547457749-24831-1-git-send-email-ying.xue@windriver.com> (raw)
Message-ID: <20190114092223.C3g7PBSilrdRgSCnSkvY0sBwsyqUy3Wn8x334l6YxdQ@z> (raw)
Recently, syzbot complained that TIPC module exits several issues
associated with uninit-value type. So, in this series, we try to
fix them as many as possible.
Ying Xue (6):
tipc: fix uninit-value in in tipc_conn_rcv_sub
tipc: fix uninit-value in tipc_nl_compat_link_reset_stats
tipc: fix uninit-value in tipc_nl_compat_bearer_enable
tipc: fix uninit-value in tipc_nl_compat_link_set
tipc: fix uninit-value in tipc_nl_compat_name_table_dump
tipc: fix uninit-value in tipc_nl_compat_doit
net/tipc/netlink_compat.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++-
net/tipc/topsrv.c | 2 +-
2 files changed, 50 insertions(+), 2 deletions(-)
--
2.7.4
next reply other threads:[~2019-01-14 9:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 9:22 Ying Xue [this message]
2019-01-14 9:22 ` [net 0/6] tipc: fix uninit-value issues reported by syzbot Ying Xue
2019-01-14 9:22 ` [net 1/6] tipc: fix uninit-value in in tipc_conn_rcv_sub Ying Xue
2019-01-14 9:22 ` Ying Xue
2019-01-14 9:22 ` [net 2/6] tipc: fix uninit-value in tipc_nl_compat_link_reset_stats Ying Xue
2019-01-14 9:22 ` Ying Xue
2019-01-14 9:22 ` [net 3/6] tipc: fix uninit-value in tipc_nl_compat_bearer_enable Ying Xue
2019-01-14 9:22 ` Ying Xue
2019-01-14 9:22 ` [net 4/6] tipc: fix uninit-value in tipc_nl_compat_link_set Ying Xue
2019-01-14 9:22 ` [net 5/6] tipc: fix uninit-value in tipc_nl_compat_name_table_dump Ying Xue
2019-01-14 9:22 ` Ying Xue
2019-01-14 9:22 ` [net 6/6] tipc: fix uninit-value in tipc_nl_compat_doit Ying Xue
2019-01-14 9:22 ` Ying Xue
2019-01-16 4:29 ` [net 0/6] tipc: fix uninit-value issues reported by syzbot 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=1547457749-24831-1-git-send-email-ying.xue@windriver.com \
--to=ying.xue@windriver.com \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
/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).