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,
stable@vger.kernel.org, yuanql9@chinatelecom.cn
Subject: Re: [PATCH v3] serial: 8250: fix shared IRQ startup race causing IRQ warning
Date: Wed, 8 Jul 2026 15:45:12 +0800 [thread overview]
Message-ID: <20260708074512.4028251-1-realwujing@gmail.com> (raw)
In-Reply-To: <20260708072306.3921604-1-wangzhaolong@fnnas.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
On Wed, Jul 08, 2026 at 03:23:06PM +0800, Wang Zhaolong wrote:
> Changes in v3:
> - Rename hash_mutex to irq_chain_mutex now that it also serializes IRQ chain
> publication and first request_irq() completion.
> - Add __must_hold() and lockdep_assert_held() to document the locking
> requirement for serial_get_or_create_irq_info().
Wang, these changes listed in your v3 changelog were all made in our
series first — by Jiri's review feedback to *our* patches, not yours:
- irq_chain_mutex rename: our v7, sent before your v3
- __must_hold() + lockdep_assert_held(): our v5, sent on Jun 24
Your v3 copies these verbatim and presents them as your own work in the
changelog. No Co-developed-by, no mention of our series at all.
The full timeline:
May 27 Wang v1 — only the THRE test race, no use-after-free fix
May 28 Our v1 — both races, full fix
May 29 Wang on our v3 thread: "v3 fixes the Bugzilla reproducer"
Jun 24 Our v5 — added __must_hold() and lockdep_assert_held()
Jul 7 Our v6 — back to guard style
Jul 8 Our v7 — renamed hash_mutex to irq_chain_mutex
Jul 8 Wang v3 — copies irq_chain_mutex rename, __must_hold(),
lockdep_assert_held() from our v5/v7
We added Co-developed-by: Wang Zhaolong to our v7. You've applied
several of our changes across your v2 and v3 without offering the same
credit. Please add the appropriate Co-developed-by tags.
Jiri has asked us to coordinate. We've been cooperative — we credited
you, we're running the same fix. Let's work together on this.
Thanks,
Jing
next prev parent reply other threads:[~2026-07-08 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 9:20 [PATCH] serial: 8250: serialize shared IRQ startup Wang Zhaolong
2026-06-24 2:49 ` Wang Zhaolong
2026-07-08 3:11 ` [PATCH v2] serial: 8250: fix shared IRQ startup race causing IRQ warning Wang Zhaolong
2026-07-08 6:03 ` Jiri Slaby
2026-07-08 6:20 ` Wang Zhaolong
2026-07-10 12:14 ` Greg KH
2026-07-08 7:23 ` [PATCH v3] " Wang Zhaolong
2026-07-08 7:45 ` Jing Wu [this message]
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=20260708074512.4028251-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=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox