From: Gui-Dong Han <2045gemini@gmail.com>
To: marcel@holtmann.org, johan.hedberg@gmail.com, luiz.dentz@gmail.com
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
baijiaju1990@outlook.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: Fix atomicity violation in {min,max}_key_size_set
Date: Thu, 11 Jan 2024 16:45:24 +0800 [thread overview]
Message-ID: <ffb39127-a462-4ce2-be37-cba8a36c8064@gmail.com> (raw)
In-Reply-To: <20231222151241.4331-1-2045gemini@gmail.com>
Dear All, I hope this message finds you well. Following up on my
previous email regarding the patch, I want to highlight an important
aspect. In /net/bluetooth/hci_debugfs.c, there are four similar bugs
related to atomicity violations, potentially leading to minimum values
exceeding maximum ones.
https://patchwork.kernel.org/project/bluetooth/patch/20231222162931.6553-1-2045gemini@gmail.com/
https://patchwork.kernel.org/project/bluetooth/patch/20231222162310.6461-1-2045gemini@gmail.com/
https://patchwork.kernel.org/project/bluetooth/patch/20231222161317.6255-1-2045gemini@gmail.com/
https://patchwork.kernel.org/project/bluetooth/patch/20231222151241.4331-1-2045gemini@gmail.com/
I kindly request your review of these issues alongside the original
patch. Understanding your busy schedules, your prompt attention to this
consolidated review would be greatly appreciated. Thank you for your
time and consideration. Best regards, Han
prev parent reply other threads:[~2024-01-11 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 15:12 [PATCH v2] Bluetooth: Fix atomicity violation in {min,max}_key_size_set Gui-Dong Han
2024-01-11 8:45 ` Gui-Dong Han [this message]
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=ffb39127-a462-4ce2-be37-cba8a36c8064@gmail.com \
--to=2045gemini@gmail.com \
--cc=baijiaju1990@outlook.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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