netdev - Re: [PATCH v2 mptcp] mptcp: fix 'scheduling while atomic' in mptcp_pm_nl_append_new_local

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250225215325.GC1867@templeofstupid.com>
Date: Tue, 25 Feb 2025 13:53:25 -0800
From: Krister Johansen <kjlx@...pleofstupid.com>
To: Matthieu Baerts <matttbe@...nel.org>
Cc: Mat Martineau <martineau@...nel.org>, Geliang Tang <geliang@...nel.org>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	Simon Horman <horms@...nel.org>, netdev@...r.kernel.org,
	mptcp@...ts.linux.dev
Subject: Re: [PATCH v2 mptcp] mptcp: fix 'scheduling while atomic' in
 mptcp_pm_nl_append_new_local_addr

Hi Matt,

On Tue, Feb 25, 2025 at 10:41:55PM +0100, Matthieu Baerts wrote:
> On 25/02/2025 20:29, Krister Johansen wrote:
> > On Tue, Feb 25, 2025 at 06:52:45PM +0100, Matthieu Baerts wrote:
> >> I'm going to apply it in our MPTCP tree, but this patch can also be
> >> directly applied in the net tree directly, not to delay it by one week
> >> if preferred. If not, I can re-send it later on.
> > 
> > Thanks, I'd be happy to send it to net directly now that it has your
> > blessing.  Would you like me to modify the call trace in the commit
> > message to match the decoded one that I included above before I send it
> > to net?
> 
> Sorry, I forgot to mention that this bit was for the net maintainers.
> Typically, trivial patches and small fixes related to MPTCP can go
> directly to net.
> 
> No need for you to re-send it. If the net maintainers prefer me to send
> it later with other patches (if any), I will update the call trace, no
> problem!

Thanks for clarifying.  I'll hold off on sending anything further and
will either let the net maintainers pick this up, or have you send it
with your next batch of patches.

Thanks again!

-K