From: Jason Gunthorpe <jgg@nvidia.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-rdma@vger.kernel.org, linux-cxl@vger.kernel.org,
linux-kernel@vger.kernel.org, Dave Jiang <dave.jiang@intel.com>,
Saeed Mahameed <saeedm@nvidia.com>
Subject: [GIT PULL] Please pull FWCTL subsystem changes
Date: Fri, 22 May 2026 20:25:01 -0300 [thread overview]
Message-ID: <20260522232501.GA1168039@nvidia.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
Hi Linus,
One fairly bad bug for PDS
Thanks,
Jason
The following changes since commit 5200f5f493f79f14bbdc349e402a40dfb32f23c8:
Linux 7.1-rc4 (2026-05-17 13:59:58 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/fwctl/fwctl.git tags/for-linus-fwctl
for you to fetch changes up to e7537735028c3ad4b0bfc02ff8fa2a1a28aa04fe:
fwctl: pds: Validate RPC input size before parsing (2026-05-19 10:44:32 -0300)
----------------------------------------------------------------
fwctl 7.1 first rc pull request
- Buffer overflow due to missing input validation in pds
----------------------------------------------------------------
Heechan Kang (1):
fwctl: pds: Validate RPC input size before parsing
drivers/fwctl/pds/main.c | 3 +++
1 file changed, 3 insertions(+)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2026-05-22 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 23:25 Jason Gunthorpe [this message]
2026-05-23 16:23 ` [GIT PULL] Please pull FWCTL subsystem changes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2026-04-16 14:11 Jason Gunthorpe
2026-04-17 4:28 ` pr-tracker-bot
2025-10-01 19:35 Jason Gunthorpe
2025-10-04 1:41 ` pr-tracker-bot
2025-04-17 12:36 Jason Gunthorpe
2025-04-17 18:57 ` pr-tracker-bot
2025-03-24 15:13 [GIT PULL] Please pull fwctl " Jason Gunthorpe
2025-03-26 17:13 ` Jakub Kicinski
2025-03-29 18:24 ` pr-tracker-bot
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=20260522232501.GA1168039@nvidia.com \
--to=jgg@nvidia.com \
--cc=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=torvalds@linux-foundation.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