From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 199637] New: UBSAN: Undefined behaviour in net/ipv4/fib_trie.c:503:6
Date: Mon, 7 May 2018 10:33:45 -0700 [thread overview]
Message-ID: <20180507103345.08e3992d@xeon-e3> (raw)
Begin forwarded message:
Date: Mon, 07 May 2018 16:07:24 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 199637] New: UBSAN: Undefined behaviour in net/ipv4/fib_trie.c:503:6
https://bugzilla.kernel.org/show_bug.cgi?id=199637
Bug ID: 199637
Summary: UBSAN: Undefined behaviour in
net/ipv4/fib_trie.c:503:6
Product: Networking
Version: 2.5
Kernel Version: 4.16.7
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
Assignee: stephen@networkplumber.org
Reporter: combuster@archlinux.us
Regression: No
After recompiling the 4.16.7 kernel with gcc 8.1, UBSAN reports the following:
[ 25.427424]
================================================================================
[ 25.429680] UBSAN: Undefined behaviour in net/ipv4/fib_trie.c:503:6
[ 25.431920] member access within null pointer of type 'struct tnode'
[ 25.434153] CPU: 3 PID: 1 Comm: systemd Not tainted 4.16.7-CUSTOM #1
[ 25.436384] Hardware name: Gigabyte Technology Co., Ltd.
H67MA-UD2H-B3/H67MA-UD2H-B3, BIOS F8 03/27/2012
[ 25.438647] Call Trace:
[ 25.440889] dump_stack+0x62/0x9f
[ 25.443104] ubsan_epilogue+0x9/0x35
[ 25.445293] handle_null_ptr_deref+0x80/0x90
[ 25.447464] __ubsan_handle_type_mismatch_v1+0x6a/0x80
[ 25.449628] tnode_free+0xce/0x120
[ 25.451749] ? replace+0xa0/0x1f0
[ 25.453833] ? resize+0x4e2/0xb70
[ 25.455916] ? __kmalloc+0x1fe/0x2d0
[ 25.457997] ? tnode_new+0x66/0x160
[ 25.460072] ? fib_insert_alias+0x4a8/0x9e0
[ 25.462145] ? fib_table_insert+0x208/0x690
[ 25.464214] ? fib_magic+0x20c/0x310
[ 25.466280] ? fib_netdev_event+0x81/0x200
[ 25.468339] ? notifier_call_chain+0x63/0x110
[ 25.470407] ? __dev_notify_flags+0xa8/0x170
[ 25.472472] ? dev_change_flags+0x56/0x80
[ 25.474538] ? do_setlink+0x3c2/0x1a00
[ 25.476603] ? fib_magic+0x20c/0x310
[ 25.478666] ? rtnl_setlink+0x129/0x1e0
[ 25.480728] ? rtnetlink_rcv_msg+0x2a4/0x7d0
[ 25.482765] ? rtnetlink_rcv+0x10/0x10
[ 25.484757] ? netlink_rcv_skb+0x6f/0x170
[ 25.486741] ? netlink_unicast+0x1c0/0x2d0
[ 25.488716] ? netlink_sendmsg+0x2c1/0x630
[ 25.490661] ? sock_sendmsg+0x49/0xb0
[ 25.492564] ? SyS_sendto+0x12b/0x1d0
[ 25.494449] ? do_syscall_64+0xad/0x5cc
[ 25.496305] ? page_fault+0x2f/0x50
[ 25.498140] ? entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 25.499974]
================================================================================
UBSAN reported nothing when the same kernel was compiled with gcc 7.3.1 from
Arch Linux repositories.
I have three more similar reports to make, if I continue to c/p in each I'm
gonna feel like a fuzzbot...
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2018-05-07 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 17:33 Stephen Hemminger [this message]
2018-06-08 0:07 ` [Bug 199637] New: UBSAN: Undefined behaviour in net/ipv4/fib_trie.c:503:6 Jakub Kicinski
2018-06-08 1:27 ` David Ahern
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=20180507103345.08e3992d@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@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 NNTP newsgroup(s).