[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220610081043.GB2146@kadam>
Date: Fri, 10 Jun 2022 11:10:43 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Thomas Osterried <thomas@...erried.de>
Cc: Eric Dumazet <edumazet@...gle.com>,
Duoming Zhou <duoming@....edu.cn>,
LKML <linux-kernel@...r.kernel.org>, jreuter@...na.de,
Ralf Bächle DL5RB <ralf@...ux-mips.org>,
David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
netdev <netdev@...r.kernel.org>, linux-hams@...r.kernel.org
Subject: Re: [PATCH net-next] ax25: Fix deadlock caused by skb_recv_datagram
in ax25_recvmsg
On Tue, Jun 07, 2022 at 11:14:34AM +0200, Thomas Osterried wrote:
> > Why is this targeting net-next tree ?
>
> Off-topic question for better understanding: when patches go to netdev,
> when to net-next tree? Ah, found explanation it here (mentioning it
> for our readers at linux-hams@):
> https://www.kernel.org/doc/Documentation/networking/netdev-FAQ.txt
>
> > 1) A fix should target net tree
> > 2) It should include a Fixes: tag
>
> tnx for info. "Fix" in subject is not enough?
>
A Fixes tag says when the bug was introduced.
regards,
dan carpenter
Powered by blists - more mailing lists