public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Cc: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	Christoph Hellwig <hch@lst.de>
Subject: [PATCH 0/3] Fixes for zoned changes in block/for-next
Date: Thu, 13 Nov 2025 22:40:25 +0900	[thread overview]
Message-ID: <20251113134028.890166-1-dlemoal@kernel.org> (raw)

Jens,

Here are 3 patches to fix 2 oops (NULL pointer dereference) and a device
mapper regression all introduced by the recent changes to blk-zoned.c
that are in block/for-next.

These are relatively simple problems that should have been discovered
right away during development. I overlooked them due to some issues (now
fixed) with my test VM environment which was not always running the
correct kernel.

Damien Le Moal (3):
  block: fix NULL pointer dereference in blk_zone_reset_all_bio_endio()
  block: fix NULL pointer dereference in disk_report_zones()
  dm: fix zone reset all operation processing

 block/blk-zoned.c    | 23 +++++++++++++----------
 drivers/md/dm-zone.c |  9 +++++++++
 2 files changed, 22 insertions(+), 10 deletions(-)

-- 
2.51.1


             reply	other threads:[~2025-11-13 13:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 13:40 Damien Le Moal [this message]
2025-11-13 13:40 ` [PATCH 1/3] block: fix NULL pointer dereference in blk_zone_reset_all_bio_endio() Damien Le Moal
2025-11-13 14:44   ` Christoph Hellwig
2025-11-13 13:40 ` [PATCH 2/3] block: fix NULL pointer dereference in disk_report_zones() Damien Le Moal
2025-11-13 14:45   ` Christoph Hellwig
2025-11-13 13:40 ` [PATCH 3/3] dm: fix zone reset all operation processing Damien Le Moal
2025-11-13 14:46   ` Christoph Hellwig
2025-11-13 16:16 ` [PATCH 0/3] Fixes for zoned changes in block/for-next Jens Axboe

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=20251113134028.890166-1-dlemoal@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.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