netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kui-Feng Lee <sinquersw@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: patchwork-bot+netdevbpf@kernel.org,
	Kui-Feng Lee <thinker.li@gmail.com>,
	davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	dsahern@kernel.org, netdev@vger.kernel.org,
	eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] ipv6: add debug checks in fib6_info_release()
Date: Thu, 7 Dec 2023 10:19:20 -0800	[thread overview]
Message-ID: <2ba1bbde-0e80-4b73-be2b-7ce27c784089@gmail.com> (raw)
In-Reply-To: <CANn89iKpM33oQ+2dwoLHzZvECAjwiKJTR3cDM64nE6VvZA99Sg@mail.gmail.com>



On 12/7/23 10:10, Eric Dumazet wrote:
> On Thu, Dec 7, 2023 at 7:06 PM Kui-Feng Lee <sinquersw@gmail.com> wrote:
> 
>> Do you happen to have a test program that can reproduce it?
> 
> syzbot has a repro, let me release the bug.
> 
> Of course syzbot bisection points to my last patch.

I just looked into the code.
The origin issue mentioned at the thread head should be something
related to a GC change I made. But, the warnings you added doesn't
catch the the error correctly.  According to your stacktrace


 > ip6_route_add+0x26/0x1f0 net/ipv6/route.c:3843
 > ipv6_route_ioctl+0x3ff/0x590 net/ipv6/route.c:4467
 > inet6_ioctl+0x265/0x2b0 net/ipv6/af_inet6.c:575
 > sock_do_ioctl+0x113/0x270 net/socket.c:1220
 > sock_ioctl+0x22e/0x6b0 net/socket.c:1339
 > vfs_ioctl fs/ioctl.c:51 [inline]
 > __do_sys_ioctl fs/ioctl.c:871 [inline]
 > __se_sys_ioctl fs/ioctl.c:857 [inline]
 > __x64_sys_ioctl+0x18f/0x210 fs/ioctl.c:857
 > do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 > do_syscall_64+0x40/0x110 arch/x86/entry/common.c:82
 > entry_SYSCALL_64_after_hwframe+0x63/0x6b

and warning messages you provided

 > WARNING: CPU: 0 PID: 5059 at include/net/ip6_fib.h:332
 > fib6_info_release include/net/ip6_fib.h:332 [inline]
 > WARNING: CPU: 0 PID: 5059 at include/net/ip6_fib.h:332
 > ip6_route_info_create+0x1a1a/0x1f10 net/ipv6/route.c:3829

It takes place in ip6_route_info_create() to do error handling.
It can be fib6_has_expires() in fib6_info_release() in this case.

  reply	other threads:[~2023-12-07 18:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 17:32 [PATCH net-next] ipv6: add debug checks in fib6_info_release() Eric Dumazet
2023-12-06  3:41 ` David Ahern
2023-12-07  3:10 ` patchwork-bot+netdevbpf
2023-12-07 13:29   ` Eric Dumazet
2023-12-07 16:43     ` Kui-Feng Lee
2023-12-07 18:06     ` Kui-Feng Lee
2023-12-07 18:10       ` Eric Dumazet
2023-12-07 18:19         ` Kui-Feng Lee [this message]
2023-12-07 18:22           ` Eric Dumazet
2023-12-07 18:25             ` David Ahern
2023-12-07 18:26               ` David Ahern
2023-12-07 18:36               ` Kui-Feng Lee
2023-12-07 18:40                 ` Kui-Feng Lee
2023-12-07 19:00                   ` Kui-Feng Lee
2023-12-07 19:05                     ` Eric Dumazet
2023-12-07 19:08                       ` Kui-Feng Lee
2023-12-07 19:14                         ` Eric Dumazet
2023-12-07 18:46             ` Kui-Feng Lee
2023-12-07 18:55               ` Eric Dumazet
2023-12-07 23:02 ` Kui-Feng Lee
2023-12-08  9:18   ` Eric Dumazet
2023-12-08 18:20     ` Kui-Feng Lee

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=2ba1bbde-0e80-4b73-be2b-7ce27c784089@gmail.com \
    --to=sinquersw@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=patchwork-bot+netdevbpf@kernel.org \
    --cc=thinker.li@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;
as well as URLs for NNTP newsgroup(s).