From: Jing Wu <realwujing@gmail.com>
To: wangzhaolong@fnnas.com
Cc: jirislaby@kernel.org, gregkh@linuxfoundation.org,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
yuanql9@chinatelecom.cn
Subject: Re: [PATCH v6] serial: 8250: fix use-after-free in IRQ chain handling
Date: Wed, 8 Jul 2026 15:57:31 +0800 [thread overview]
Message-ID: <20260708075732.4139996-1-realwujing@gmail.com> (raw)
In-Reply-To: <5cf37150673ea4d5c28f94db91cdf68504b50522.0e091ec2.1d26.4eb2.8da3.53f8a6520707@feishu.cn>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On Wed, Jul 08, 2026 at 03:33:36PM +0800, Wang Zhaolong wrote:
> I do not want to make this a patch ownership discussion.
Let's be clear about the facts, then.
You reported the bug. Our team fixed it — the next day. May 28, our
v1. You confirmed on May 29 that our v3 fixes your reproducer.
Since then, you've posted three versions — v1, v2, v3 — that
incrementally copy the work we developed and refined through seven
iterations. Your v2 copied our lock-move skeleton. Your v3 copied the
irq_chain_mutex rename, __must_hold(), and lockdep_assert_held() — all
written by us, all reviewed by Jiri on our patches.
You list these as your own "Changes in v3" with zero attribution.
This is not a "patch ownership discussion." You copied our code. The
kernel is GPLv2 — that means you can use the code, but you must
preserve the copyright notices. Co-developed-by is the mechanism for
that.
You reported the bug — we fixed it first. We credited you. Now add
the tags.
Jing
next prev parent reply other threads:[~2026-07-08 7:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 14:06 [PATCH v6] serial: 8250: fix use-after-free in IRQ chain handling Qiliang Yuan
2026-07-08 6:03 ` Jiri Slaby
2026-07-08 6:34 ` Jing Wu
2026-07-08 7:11 ` Jing Wu
2026-07-08 7:33 ` Wang Zhaolong
2026-07-08 7:57 ` Jing Wu [this message]
2026-07-08 8:20 ` Wang Zhaolong
2026-07-08 7:39 ` Jing Wu
2026-07-08 7:53 ` Wang Zhaolong
2026-07-08 8:08 ` Jing Wu
2026-07-08 8:32 ` Wang Zhaolong
[not found] ` <5cf37150673ea4d5c28f94db91cdf68504b50522.9be37cbd.7a04.4d7e.b20e.d3f90675af6e@feishu.cn>
2026-07-10 12:17 ` Greg KH
2026-07-10 13:15 ` Wang Zhaolong
2026-07-10 13:28 ` Greg KH
2026-07-08 8:43 ` Jing Wu
2026-07-08 8:45 ` Jing Wu
-- strict thread matches above, loose matches on Subject: below --
2026-05-27 9:20 [PATCH] serial: 8250: serialize shared IRQ startup Wang Zhaolong
2026-07-08 3:11 ` [PATCH v2] serial: 8250: fix shared IRQ startup race causing IRQ warning Wang Zhaolong
2026-07-08 7:23 ` [PATCH v3] " Wang Zhaolong
2026-07-08 8:47 ` [PATCH v6] serial: 8250: fix use-after-free in IRQ chain handling Jing Wu
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=20260708075732.4139996-1-realwujing@gmail.com \
--to=realwujing@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=wangzhaolong@fnnas.com \
--cc=yuanql9@chinatelecom.cn \
/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.