[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8e9a1c59f78a7774268bb6defed46df6f3771cbc.camel@redhat.com>
Date: Tue, 28 May 2024 11:40:38 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: lars@...bit.com, linux-hams@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH v4] ax25: Fix refcount imbalance on inbound connections
On Wed, 2024-05-22 at 14:31 -0400, lars@...bit.com wrote:
> From: Lars Kellogg-Stedman <lars@...bit.com>
>
> When releasing a socket in ax25_release(), we call netdev_put() to
> decrease the refcount on the associated ax.25 device. However, the
> execution path for accepting an incoming connection never calls
> netdev_hold(). This imbalance leads to refcount errors, and ultimately
> to kernel crashes.
>
> A typical call trace for the above situation looks like this:
>
> Call Trace:
> <TASK>
> ? show_regs+0x64/0x70
> ? __warn+0x83/0x120
> ? refcount_warn_saturate+0xb2/0x100
> ? report_bug+0x158/0x190
> ? prb_read_valid+0x20/0x30
> ? handle_bug+0x3e/0x70
> ? exc_invalid_op+0x1c/0x70
> ? asm_exc_invalid_op+0x1f/0x30
> ? refcount_warn_saturate+0xb2/0x100
> ? refcount_warn_saturate+0xb2/0x100
> ax25_release+0x2ad/0x360
> __sock_release+0x35/0xa0
> sock_close+0x19/0x20
> [...]
>
> On reboot (or any attempt to remove the interface), the kernel gets
> stuck in an infinite loop:
>
> unregister_netdevice: waiting for ax0 to become free. Usage count = 0
>
> This patch corrects these issues by ensuring that we call netdev_hold()
> and ax25_dev_hold() for new connections in ax25_accept().
>
> Fixes: 7d8a3a477b ("ax25: Fix ax25 session cleanup problems")
Note that the fixes tag above is still wrong - the hash must be 12
chars long, see:
https://elixir.bootlin.com/linux/v6.10-rc1/source/Documentation/process/5.Posting.rst#L207
so regardless of Dan's eventual ack you will have to repost this patch.
Please run checkpatch locally before the next submission, thanks,
Paolo
Powered by blists - more mailing lists