From: zhulei <zhulei_szu@163.com>
To: ap420073@gmail.com
Cc: davem@davemloft.net, jbenc@redhat.com, sashal@kernel.org,
stable@vger.kernel.org, gregkh@linuxfoundation.org
Subject: 4.19 stable kernel crash caused by vxlan testing
Date: Tue, 23 Apr 2024 13:52:40 +0800 (CST) [thread overview]
Message-ID: <715eaf46.7523.18f098372d3.Coremail.zhulei_szu@163.com> (raw)
Hey all,
I recently used a testing program to test the 4.19 stable branch kernel and found that a crash occurred immediately. The test source code link is:
https://github.com/Backmyheart/src0358/blob/master/vxlan_fdb_destroy.c
The test command is as follows:
gcc vxlan_fdb_destroy.c -o vxlan_fdb_destroy -lpthread
According to its stack, upstream has relevant repair patch, the commit id is 7c31e54aeee517d1318dfc0bde9fa7de75893dc6.
May i ask if the 4.19 kernel will port this patch ?
next reply other threads:[~2024-04-23 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 5:52 zhulei [this message]
2024-04-23 11:04 ` 4.19 stable kernel crash caused by vxlan testing Taehee Yoo
2024-04-23 11:11 ` Greg KH
2024-05-07 9:20 ` zhulei
2024-05-13 13:03 ` Greg KH
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=715eaf46.7523.18f098372d3.Coremail.zhulei_szu@163.com \
--to=zhulei_szu@163.com \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jbenc@redhat.com \
--cc=sashal@kernel.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).