From: Abinash Singh <abinashsinghlalotra@gmail.com>
To: martin.petersen@oracle.com, James.Bottomley@HansenPartnership.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
bvanassche@acm.org, abinashsinghlalotra@gmail.com,
dlemoal@kernel.org
Subject: [PATCH v8 0/2] scsi: sd: Fix build warning in sd_revalidate_disk()
Date: Wed, 20 Aug 2025 20:15:08 +0530 [thread overview]
Message-ID: <20250820144511.15329-1-abinashsinghlalotra@gmail.com> (raw)
Hi all,
This v8 series follows up on v7 of the
"scsi: sd: Fix build warning in sd_revalidate_disk()" patches.
On Tue, 19 Aug 2025 Bart Van Assche wrote:
> The traditional order for kfree() statements is the opposite order of
> the corresponding kmalloc() calls.
>
> Shouldn't this patch remove the initializer from the 'err' variable?
> Otherwise this patch looks good to me.
Based on Bart’s feedback, I have addressed the following in v8:
Changes in v8:
- Patch 1/2:
* Reverse the order of kfree() calls to follow the conventional
opposite-of-kmalloc() order.
* Added Bart Van Assche’s Reviewed-by tag.
- Patch 2/2:
* Removed the unused ‘err’ variable initializer.
As before, the first patch fixes the stack usage warning by moving a
large struct off the stack (with Fixes and Cc: stable tags). The second
patch then simplifies sd_revalidate_disk() by making it return void.
Many thanks to Bart and Damien for their reviews and guidance.
Abinash Singh (2):
scsi: sd: Fix build warning in sd_revalidate_disk()
scsi: sd: make sd_revalidate_disk() return void
drivers/scsi/sd.c | 56 +++++++++++++++++++++++++++--------------------
1 file changed, 32 insertions(+), 24 deletions(-)
--
2.43.0
next reply other threads:[~2025-08-20 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 14:45 Abinash Singh [this message]
2025-08-20 14:45 ` [PATCH v8 1/2] " Abinash Singh
2025-08-22 19:47 ` Bart Van Assche
2025-08-24 16:29 ` Abinash Singh
2025-08-20 14:45 ` [PATCH v8 2/2] scsi: sd: make sd_revalidate_disk() return void Abinash Singh
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=20250820144511.15329-1-abinashsinghlalotra@gmail.com \
--to=abinashsinghlalotra@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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
all inboxes | Powered by JetHome®