From: Andrew Lunn <andrew@lunn.ch>
To: "Peter Münster" <pm@a16n.net>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org,
Michael Chan <michael.chan@broadcom.com>
Subject: Re: [PATCH net v2] net: b44: set pause params only when interface is up
Date: Fri, 19 Apr 2024 21:06:22 +0200 [thread overview]
Message-ID: <3615d058-13c7-4e51-9299-e994ca9c13f3@lunn.ch> (raw)
In-Reply-To: <875xwd1g44.fsf@a16n.net>
On Fri, Apr 19, 2024 at 06:17:47PM +0200, Peter Münster wrote:
> Hi,
>
> This patch fixes a kernel panic when using netifd.
> Could you please apply it also to linux-5.15.y at least?
>
> TIA and kind regards,
> --
> Peter
Hi Peter
This is better, but still has some process issues.
> b44_free_rings() accesses b44::rx_buffers (and ::tx_buffers)
> unconditionally, but b44::rx_buffers is only valid when the
> device is up (they get allocated in b44_open(), and deallocated
> again in b44_close()), any other time these is just a NULL pointers.
>
> So if you try to change the pause params while the network interface
> is disabled/administratively down, everything explodes (which likely
> netifd tries to do).
>
> Link: https://github.com/openwrt/openwrt/issues/13789
> Fixes: 1da177e4c3f4 (Linux-2.6.12-rc2)
Cc: stable@vger.kernel.org
needs to go here. Your patch will first get applied to the next -rc
release. Once it is published there, any patches with this tag are
automatically added to the list for backporting to stable. That will
include all long term stable branches, so there is no need to request
specifically linux-5.15.
There is some documentation about this here:
https://www.kernel.org/doc/Documentation/process/stable-kernel-rules.rst
> Reported-by: Peter Münster <pm@a16n.net>
> Suggested-by: Jonas Gorski <jonas.gorski@gmail.com>
> Signed-off-by: Vaclav Svoboda <svoboda@neng.cz>
> Tested-by: Peter Münster <pm@a16n.net>
> Signed-off-by: Peter Münster <pm@a16n.net>
> ---
Anything above the --- gets merged as the commit message. Anything
below it and the patch proper gets discarded. This is where you can
add comments for Maintainers etc. For this patch, you don't actually
need any such comments.
I often say to mainline newbies: The code is easy, the hard bit is the
processes.
Andrew
prev parent reply other threads:[~2024-04-19 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 16:17 [PATCH net v2] net: b44: set pause params only when interface is up Peter Münster
2024-04-19 19:06 ` Andrew Lunn [this message]
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=3615d058-13c7-4e51-9299-e994ca9c13f3@lunn.ch \
--to=andrew@lunn.ch \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pm@a16n.net \
--cc=stable@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