From: Dan Carpenter <dan.carpenter@oracle.com>
To: Thomas Osterried <thomas@osterried.de>
Cc: "Eric Dumazet" <edumazet@google.com>,
"Duoming Zhou" <duoming@zju.edu.cn>,
LKML <linux-kernel@vger.kernel.org>,
jreuter@yaina.de, "Ralf Bächle DL5RB" <ralf@linux-mips.org>,
"David Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
netdev <netdev@vger.kernel.org>,
linux-hams@vger.kernel.org
Subject: Re: [PATCH net-next] ax25: Fix deadlock caused by skb_recv_datagram in ax25_recvmsg
Date: Fri, 10 Jun 2022 11:10:43 +0300 [thread overview]
Message-ID: <20220610081043.GB2146@kadam> (raw)
In-Reply-To: <E5F82D12-56D3-4040-A92B-C658772FD8DD@osterried.de>
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
next prev parent reply other threads:[~2022-06-10 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 16:21 [PATCH net-next] ax25: Fix deadlock caused by skb_recv_datagram in ax25_recvmsg Duoming Zhou
2022-06-06 17:31 ` Eric Dumazet
2022-06-07 9:14 ` Thomas Osterried
2022-06-10 8:10 ` Dan Carpenter [this message]
2022-06-07 12:20 ` duoming
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=20220610081043.GB2146@kadam \
--to=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=duoming@zju.edu.cn \
--cc=edumazet@google.com \
--cc=jreuter@yaina.de \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ralf@linux-mips.org \
--cc=thomas@osterried.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.