From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: martin.petersen@oracle.com, Li Qiang <liqiang01@kylinos.cn>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2 0/6] scsi: ufs: Fix descriptor parsing and invalid input handling
Date: Thu, 06 Aug 2026 15:34:47 -0400 [thread overview]
Message-ID: <yq1wlu33v9u.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <25919cf5-2e3a-4baf-a362-748d40f956a7@acm.org> (Bart Van Assche's message of "Tue, 4 Aug 2026 21:59:11 -0700")
Hi Bart!
> Can you please take a look at this patch series? Patch 1/6 has already
> been backported to an internal Android kernel 6.18 development branch
> because it fixes a buffer overflow we ran into on an emulator
> environment.
I had already merged this series but must have missed it during one of
the many Sashiko-compelled rebases this cycle. Now re-merged into
7.3/scsi-staging.
Thanks!
--
Martin K. Petersen
prev parent reply other threads:[~2026-08-06 19:35 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 6:19 [PATCH 0/5] scsi: ufs: Fix descriptor parsing and invalid input handling liqiang
2026-07-16 6:19 ` [PATCH 1/5] scsi: ufs: core: Validate string descriptors liqiang
2026-07-16 17:47 ` Bart Van Assche
2026-07-17 15:35 ` Li Qiang
2026-07-16 6:19 ` [PATCH 2/5] scsi: ufs: Fix NULL dereferences after tag lookup liqiang
2026-07-16 6:43 ` sashiko-bot
2026-07-16 17:52 ` Bart Van Assche
2026-07-16 6:19 ` [PATCH 3/5] scsi: ufs: core: Validate connected lane counts liqiang
2026-07-16 6:19 ` [PATCH 4/5] scsi: ufs: rpmb: Validate frame before parsing liqiang
2026-07-16 6:28 ` sashiko-bot
2026-07-16 17:58 ` Bart Van Assche
2026-07-16 6:19 ` [PATCH 5/5] scsi: ufs: debugfs: Reserve space for a string terminator liqiang
2026-07-16 17:56 ` Bart Van Assche
2026-07-16 17:42 ` [PATCH 0/5] scsi: ufs: Fix descriptor parsing and invalid input handling Bart Van Assche
2026-07-17 15:16 ` Li Qiang
2026-07-17 15:39 ` [PATCH v2 0/6] " Li Qiang
2026-07-17 15:39 ` [PATCH v2 1/6] scsi: ufs: core: Validate string descriptors Li Qiang
2026-07-20 9:13 ` Peter Wang (王信友)
2026-07-22 18:06 ` Bart Van Assche
2026-07-17 15:39 ` [PATCH v2 2/6] scsi: ufs: Avoid NULL CQE dereference when reporting invalid tags Li Qiang
2026-07-20 9:14 ` Peter Wang (王信友)
2026-07-22 18:07 ` Bart Van Assche
2026-07-17 15:39 ` [PATCH v2 3/6] scsi: ufs: core: Validate connected lane counts Li Qiang
2026-07-17 16:21 ` sashiko-bot
2026-07-17 15:39 ` [PATCH v2 4/6] scsi: ufs: rpmb: Validate request frame length before parsing Li Qiang
2026-07-17 16:32 ` sashiko-bot
2026-07-20 9:15 ` Peter Wang (王信友)
2026-07-22 12:04 ` Bean Huo
2026-07-17 15:39 ` [PATCH v2 5/6] scsi: ufs: rpmb: Use unaligned accessors for RPMB frames Li Qiang
2026-07-17 16:54 ` sashiko-bot
2026-07-20 9:15 ` Peter Wang (王信友)
2026-07-22 12:33 ` Bean Huo
2026-07-22 13:54 ` Bart Van Assche
2026-07-23 8:12 ` David Laight
2026-07-17 15:39 ` [PATCH v2 6/6] scsi: ufs: debugfs: Reserve space for a string terminator Li Qiang
2026-07-20 9:16 ` Peter Wang (王信友)
2026-07-22 18:08 ` Bart Van Assche
2026-08-05 4:59 ` [PATCH v2 0/6] scsi: ufs: Fix descriptor parsing and invalid input handling Bart Van Assche
2026-08-06 19:34 ` Martin K. Petersen [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=yq1wlu33v9u.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=bvanassche@acm.org \
--cc=linux-scsi@vger.kernel.org \
--cc=liqiang01@kylinos.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