All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: xiujianfeng <xiujianfeng@huawei.com>, <netdev@vger.kernel.org>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	mst@redhat.com, jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
	virtualization@lists.linux.dev
Subject: Re: [BUG REPORT] kernel BUG at lib/dynamic_queue_limits.c:99!
Date: Fri, 12 Jul 2024 17:43:21 -0700	[thread overview]
Message-ID: <20240712174321.603b4436@kernel.org> (raw)
In-Reply-To: <8036617e-62f3-17cb-f43a-80531e10e241@huawei.com>

CC: virtio_net maintainers and Jiri who added BQL

On Fri, 12 Jul 2024 10:12:42 +0800 xiujianfeng wrote:
> On 2024/7/12 10:08, xiujianfeng wrote:
> > I found a problem with my QEMU environment, and the log is as follows.
> > 
> > After I did the bisect to locate the issue, I found
> > 8490dd0592e85e0cceefa6b48d66dbdd73df0fb3 is the first bad commit,
> > however this is a merge commit, and I cannot further confirm which
> > specific commit caused this issue.  
> 
> It's on
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git and
> the base commit is f477dd6eede3
> 
> > 
> > ------------[ cut here ]------------
> > kernel BUG at lib/dynamic_queue_limits.c:99!
> > Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
> > CPU: 1 UID: 0 PID: 203 Comm: ip Not tainted
> > 6.10.0-rc7-next-20240711-12643-gf477dd6eede3 #613
> > Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1
> > 04/01/2014
> > RIP: 0010:dql_completed+0x212/0x230
> > Code: 41 1c 01 48 89 57 58 e9 85 fe ff ff 85 ed 40 0f 95 c5 41 39 d8 0f
> > 95 c1 40 84 cd 74 05 45 85 e4 78 0a 44 89 d9 e9 67 fe fe
> > RSP: 0018:ffffc900000f0d70 EFLAGS: 00000213
> > RAX: 0000000000000000 RBX: ffff88800413b800 RCX: ffff888005925240
> > RDX: 0000000000000000 RSI: 0000000081df1116 RDI: ffff888003a0d700
> > RBP: ffff888003a0d600 R08: 0000000000000000 R09: 0000000000000000
> > R10: 0000000000000000 R11: ffff88800a403c90 R12: 0000000000000001
> > R13: ffffc900000f0db0 R14: ffff888003a0d680 R15: ffff88803cc80000
> > FS:  00007fcf4229f1c0(0000) GS:ffff88803cc80000(0000) knlGS:0000000000000000
> > CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > CR2: 00005596d60d1290 CR3: 00000000093c0000 CR4: 00000000000006f0
> > Call Trace:
> >  <IRQ>
> >  ? die+0x32/0x90
> >  ? do_trap+0xdc/0x100
> >  ? dql_completed+0x212/0x230
> >  ? do_error_trap+0x60/0x80
> >  ? dql_completed+0x212/0x230
> >  ? exc_invalid_op+0x4f/0x70
> >  ? dql_completed+0x212/0x230
> >  ? asm_exc_invalid_op+0x1a/0x20
> >  ? dql_completed+0x212/0x230
> >  __free_old_xmit+0xb2/0x120
> >  free_old_xmit+0x23/0x70
> >  ? _raw_spin_trylock+0x46/0x60
> >  virtnet_poll+0xe0/0x590
> >  ? update_curr+0xf9/0x1c0
> >  ? find_held_lock+0x2b/0x80
> >  __napi_poll+0x25/0x160
> >  net_rx_action+0x177/0x310
> >  ? clockevents_program_event+0x53/0x100
> >  ? lock_release+0xa4/0x1d0
> >  ? ktime_get+0x76/0x100
> >  ? lapic_next_event+0x10/0x20
> >  handle_softirqs+0xd0/0x210
> >  do_softirq+0x3b/0x60
> >  </IRQ>
> >  <TASK>
> >  __local_bh_enable_ip+0x55/0x70
> >  virtnet_open+0xac/0x2d0
> >  __dev_open+0xda/0x190
> >  __dev_change_flags+0x1b3/0x230
> >  ? __pfx_stack_trace_consume_entry+0x10/0x10
> >  ? arch_stack_walk+0x9d/0xf0
> >  dev_change_flags+0x20/0x60
> >  do_setlink+0x27e/0x1120
> >  ? set_track_prepare+0x3b/0x60
> >  ? rtnl_newlink+0x5a/0xa0
> >  ? rtnetlink_rcv_msg+0x199/0x4c0
> >  ? __nla_validate_parse+0x5e/0xed0
> >  ? netlink_sendmsg+0x1e3/0x420
> >  ? __sock_sendmsg+0x5e/0x60
> >  ? ____sys_sendmsg+0x1da/0x210
> >  ? ___sys_sendmsg+0x7b/0xc0
> >  ? __sys_sendmsg+0x50/0x90
> >  ? do_syscall_64+0x4b/0x110
> >  ? entry_SYSCALL_64_after_hwframe+0x76/0x7e
> >  __rtnl_newlink+0x50d/0x990
> >  ? __kmalloc_cache_noprof+0x1a0/0x260
> >  ? __kmalloc_cache_noprof+0x204/0x260
> >  ? rtnetlink_rcv_msg+0x14e/0x4c0
> >  ? rtnl_newlink+0x5a/0xa0
> >  rtnl_newlink+0x73/0xa0
> >  rtnetlink_rcv_msg+0x199/0x4c0
> >  ? find_held_lock+0x2b/0x80
> >  ? __pfx_rtnetlink_rcv_msg+0x10/0x10
> >  netlink_rcv_skb+0x56/0x100
> >  ? netlink_unicast+0x69/0x3a0
> >  netlink_unicast+0x283/0x3a0
> >  netlink_sendmsg+0x1e3/0x420
> >  __sock_sendmsg+0x5e/0x60
> >  ____sys_sendmsg+0x1da/0x210
> >  ? copy_msghdr_from_user+0x68/0xa0
> >  ___sys_sendmsg+0x7b/0xc0
> >  ? stack_depot_save_flags+0x2e/0x8a0
> >  ? check_bytes_and_report.constprop.0+0x48/0x120
> >  ? check_object+0xb5/0x3a0
> >  ? find_held_lock+0x2b/0x80
> >  __sys_sendmsg+0x50/0x90
> >  do_syscall_64+0x4b/0x110
> >  entry_SYSCALL_64_after_hwframe+0x76/0x7e
> > RIP: 0033:0x7fcf423c7f03
> > Code: 64 89 02 48 c7 c0 ff ff ff ff eb b7 66 2e 0f 1f 84 00 00 00 00 00
> > 90 64 8b 04 25 18 00 00 00 85 c0 75 14 b8 2e 00 00 00 08
> > RSP: 002b:00007ffcbfa59528 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
> > RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcf423c7f03
> > RDX: 0000000000000000 RSI: 00007ffcbfa59590 RDI: 0000000000000003
> > RBP: 0000000066907e78 R08: 0000000000000001 R09: 00007fcf42499be0
> > R10: 0000000000000076 R11: 0000000000000246 R12: 0000000000000001
> > R13: 00007ffcbfa59660 R14: 0000000000000000 R15: 00005596d6088020
> >  </TASK>
> > Modules linked in:
> > ---[ end trace 0000000000000000 ]---
> > RIP: 0010:dql_completed+0x212/0x230
> > Code: 41 1c 01 48 89 57 58 e9 85 fe ff ff 85 ed 40 0f 95 c5 41 39 d8 0f
> > 95 c1 40 84 cd 74 05 45 85 e4 78 0a 44 89 d9 e9 67 fe fe
> > RSP: 0018:ffffc900000f0d70 EFLAGS: 00000213
> > RAX: 0000000000000000 RBX: ffff88800413b800 RCX: ffff888005925240
> > RDX: 0000000000000000 RSI: 0000000081df1116 RDI: ffff888003a0d700
> > RBP: ffff888003a0d600 R08: 0000000000000000 R09: 0000000000000000
> > R10: 0000000000000000 R11: ffff88800a403c90 R12: 0000000000000001
> > R13: ffffc900000f0db0 R14: ffff888003a0d680 R15: ffff88803cc80000
> > FS:  00007fcf4229f1c0(0000) GS:ffff88803cc80000(0000) knlGS:0000000000000000
> > CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > CR2: 00005596d60d1290 CR3: 00000000093c0000 CR4: 00000000000006f0
> > Kernel panic - not syncing: Fatal exception in interrupt
> > Kernel Offset: disabled
> > ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]---
> >   
> 


  reply	other threads:[~2024-07-13  0:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12  2:08 [BUG REPORT] kernel BUG at lib/dynamic_queue_limits.c:99! xiujianfeng
2024-07-12  2:12 ` xiujianfeng
2024-07-13  0:43   ` Jakub Kicinski [this message]
2024-07-13  0:44     ` Jakub Kicinski
2024-07-16 11:31       ` xiujianfeng

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=20240712174321.603b4436@kernel.org \
    --to=kuba@kernel.org \
    --cc=jasowang@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux.dev \
    --cc=xiujianfeng@huawei.com \
    --cc=xuanzhuo@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.