From: 성병찬 <tjdqudcks0424@naver.com>
To: <netdev-bot+sinfo@kernel.org>
Cc: "Manivannan Sadhasivam" <mani@kernel.org>,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net] qrtr: make repeated lookups from one client idempotent
Date: Thu, 08 Oct 2026 17:38:57 +0900 [thread overview]
Message-ID: <246918dc4bb12e46eef07cfeb6b3d1e5@cweb010.nm> (raw)
In-Reply-To: <179144819826.2527009.1542482431321559008@kernel.org>
Hi,
This issue was identified during manual static source review of the QRTR
lookup accounting path, with assistance from OpenAI Codex.
I subsequently reproduced and validated it using an isolated local
AF_QIPCRTR fixture. A separate unprivileged socket was unable to register
a lookup after one client submitted 128 duplicate lookup requests in all
three baseline runs. With the patch applied, the independent lookup
succeeded in all three runs, while the boundary, repeated-listing, and
socket-close cleanup controls retained their expected behavior.
Thanks,
Sung Byeongchan
prev parent reply other threads:[~2026-10-08 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 8:25 [PATCH net] qrtr: make repeated lookups from one client idempotent Sung Byeongchan
2026-10-08 8:29 ` netdev-bot+sinfo
2026-10-08 8:38 ` 성병찬 [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=246918dc4bb12e46eef07cfeb6b3d1e5@cweb010.nm \
--to=tjdqudcks0424@naver.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mani@kernel.org \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@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