From: Greg KH <gregkh@linuxfoundation.org>
To: "Марк Коренберг" <socketpair@gmail.com>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: kernel BUG on network namespace deletion
Date: Mon, 15 Jan 2024 13:01:21 +0100 [thread overview]
Message-ID: <2024011533-kebab-headway-0461@gregkh> (raw)
In-Reply-To: <CAEmTpZHcXrPTC15KS9SvC6auK1G2nugny_wQA411+9CXrW0dgQ@mail.gmail.com>
On Mon, Jan 15, 2024 at 03:00:36PM +0500, Марк Коренберг wrote:
> Hi, netdev. I have found a bug in the Linux Kernel. Please take a look.
That's not a good way to post, sorry. Also what does this have to do
with stable@?
Please resend your original message to netdev, top-posting doesn't go
very well here, as per the email guidelines in our documentation :)
thanks,
greg k-h
next prev parent reply other threads:[~2024-01-15 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEmTpZHU5JBkQOVWvp4i2f02et2e0v9mTFzhmxhFOE47xPyqYg@mail.gmail.com>
[not found] ` <2024011517-nursery-flinch-3101@gregkh>
2024-01-15 10:00 ` kernel BUG on network namespace deletion Марк Коренберг
2024-01-15 12:01 ` Greg KH [this message]
2024-01-15 13:59 Kernel " Марк Коренберг
2024-01-19 0:49 ` Jakub Kicinski
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=2024011533-kebab-headway-0461@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
--cc=socketpair@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).