lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 19 Aug 2014 10:56:15 -0400 From: Chuck Lever <chuck.lever@...cle.com> To: Bart Van Assche <bvanassche@....org> Cc: netdev@...r.kernel.org, linux-rdma <linux-rdma@...r.kernel.org> Subject: Re: 3.17-rc1 oops during network interface configuration On Aug 18, 2014, at 8:18 AM, Bart Van Assche <bvanassche@....org> wrote: > Hello, > > Has anyone else already tried to boot kernel 3.17-rc1 on an IB system ? After updating to 3.17-rc1 this morning, I hit the same issue. > The > following call trace is triggered during boot on a system on which kernel > 3.16 runs fine: > > BUG: unable to handle kernel paging request at ffff88090000007e > IP: __dev_queue_xmit+0x519 > Call Trace: > ? __dev_queue_xmit+0x49 > dev_queue_xmit+0x10 > neigh_connected_output > ? ip_finish_output > ip_finish_output > ? ip_finish_output > ? netif_rx_ni > ip_mc_output > ip_local_out_sk > ip_send_skb > udp_send_skb > udp_sendmsg > ? ip_reply_glue_bits > ? __lock_is_held > inet_sendmsg > ? inet_sendmsg > sock_sendmsg > ? might_fault > ? might_fault > ? move_addr_to_kernel.part.38 > SYSC_sendto > ? sysret_check > ? trace_hardirqs_on_caller > ? trace_hardirqs_on_thunk > SyS_sendto > system_call_fastpath > > Kernel panic - not syncing: Fatal exception in interrupt > Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff) > drm_kms_helper: panic occurred, switching back to text console > > A screenshot of this kernel oops can be found here: > https://drive.google.com/file/d/0B1YQOreL3_FxVDB5UTNwekF6LVU/ > > gdb translates the crash address into the following (not sure this makes sense > since offset 0x519 is past the end of __dev_queue_xmit()): > > (gdb) list *(__dev_queue_xmit+0x519) > 0xffffffff8136bc89 is in netdev_adjacent_rename_links (net/core/dev.c:5167). > 5162 void netdev_adjacent_rename_links(struct net_device *dev, char *oldname) > 5163 { > 5164 struct netdev_adjacent *iter; > 5165 > 5166 list_for_each_entry(iter, &dev->adj_list.upper, list) { > 5167 netdev_adjacent_sysfs_del(iter->dev, oldname, > 5168 &iter->dev->adj_list.lower); > 5169 netdev_adjacent_sysfs_add(iter->dev, dev, > 5170 &iter->dev->adj_list.lower); > 5171 } > > And the address __dev_queue_xmit+0x49 is translated by gdb into: > > (gdb) list *(__dev_queue_xmit+0x49) > 0xffffffff8136b7b9 is in __dev_queue_xmit (./arch/x86/include/asm/preempt.h:75). > 70 * The various preempt_count add/sub methods > 71 */ > 72 > 73 static __always_inline void __preempt_count_add(int val) > 74 { > 75 raw_cpu_add_4(__preempt_count, val); > 76 } > 77 > 78 static __always_inline void __preempt_count_sub(int val) > 79 { > > Bart. > -- > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Chuck Lever chuck[dot]lever[at]oracle[dot]com -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists