public inbox for linux-kernel-mentees@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: martin.petersen@oracle.com, Shaurya Rane <ssrane_b23@ee.vjti.ac.in>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	 skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev,
	 david.hunter.linux@gmail.com, khalid@kernel.org,
	 syzbot+527a7e48a3d3d315d862@syzkaller.appspotmail.com,
	 Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] block: fix memory leak in __blkdev_issue_zero_pages
Date: Thu, 04 Dec 2025 11:20:37 -0700	[thread overview]
Message-ID: <176487243751.985814.383120227280182840.b4-ty@kernel.dk> (raw)
In-Reply-To: <20251204181259.23864-1-ssrane_b23@ee.vjti.ac.in>


On Thu, 04 Dec 2025 23:42:59 +0530, Shaurya Rane wrote:
> Move the fatal signal check before bio_alloc() to prevent a memory
> leak when BLKDEV_ZERO_KILLABLE is set and a fatal signal is pending.
> 
> Previously, the bio was allocated before checking for a fatal signal.
> If a signal was pending, the code would break out of the loop without
> freeing or chaining the just-allocated bio, causing a memory leak.
> 
> [...]

Applied, thanks!

[1/1] block: fix memory leak in __blkdev_issue_zero_pages
      commit: 220d82ee063a38fcdc658b8d4274f59de4398dd0

Best regards,
-- 
Jens Axboe




      reply	other threads:[~2025-12-04 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 18:12 [PATCH] block: fix memory leak in __blkdev_issue_zero_pages Shaurya Rane
2025-12-04 18:20 ` Jens Axboe [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=176487243751.985814.383120227280182840.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=david.hunter.linux@gmail.com \
    --cc=kbusch@kernel.org \
    --cc=khalid@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=skhan@linuxfoundation.org \
    --cc=ssrane_b23@ee.vjti.ac.in \
    --cc=syzbot+527a7e48a3d3d315d862@syzkaller.appspotmail.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