public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
* add a "discard cache" debug option to zloop
@ 2026-03-18  5:53 Christoph Hellwig
  2026-03-18  5:53 ` [PATCH 1/2] zloop: refactor zloop_rw Christoph Hellwig
  2026-03-18  5:53 ` [PATCH 2/2] zloop: forget write cache on force removal Christoph Hellwig
  0 siblings, 2 replies; 8+ messages in thread
From: Christoph Hellwig @ 2026-03-18  5:53 UTC (permalink / raw)
  To: Damien Le Moal, Jens Axboe; +Cc: linux-block

Hi all,

this series adds a new option to zloop to lose data not committed to stable
storage using a flush operation on device removal.  The idea is to help
testing that file system code does the right thing in face of volatile
write caches.  For conventional devices, this can be tested using
dm-log-writes, but the concepts there don't work for sequential write
required zones.  Instead this adds an option to zloop, which records the
write pointer at the last cache flush for each zone file in an xattr,
and truncates the files down to that value on removal, simulating losing
the contents of the volatile write cache.

Diffstat:
 Documentation/admin-guide/blockdev/zoned_loop.rst |    5 
 drivers/block/zloop.c                             |  337 ++++++++++++++--------
 2 files changed, 226 insertions(+), 116 deletions(-)

^ permalink raw reply	[flat|nested] 8+ messages in thread
* add a "discard cache" debug option to zloop v2
@ 2026-03-19  6:02 Christoph Hellwig
  2026-03-19  6:02 ` [PATCH 1/2] zloop: refactor zloop_rw Christoph Hellwig
  0 siblings, 1 reply; 8+ messages in thread
From: Christoph Hellwig @ 2026-03-19  6:02 UTC (permalink / raw)
  To: Damien Le Moal, Jens Axboe; +Cc: linux-block

Hi all,

this series adds a new option to zloop to lose data not committed to
stable storage using a flush operation on device removal.  The idea is
to help testing that file system code does the right thing in face of
volatile write caches.  For conventional devices, this can be tested
using dm-log-writes, but the concepts there don't work for sequential
write required zones.  Instead this adds an option to zloop, which
records the write pointer at the last cache flush for each zone file in
an xattr, and truncates the files down to that value on removal,
simulating losing the contents of the volatile write cache.

Changes since v1:
 - fix up the documentation

Diffstat:
 Documentation/admin-guide/blockdev/zoned_loop.rst |    5 
 drivers/block/zloop.c                             |  337 ++++++++++++++--------
 2 files changed, 226 insertions(+), 116 deletions(-)

^ permalink raw reply	[flat|nested] 8+ messages in thread
* add a "discard cache" debug option to zloop v3
@ 2026-03-23  7:11 Christoph Hellwig
  2026-03-23  7:11 ` [PATCH 1/2] zloop: refactor zloop_rw Christoph Hellwig
  0 siblings, 1 reply; 8+ messages in thread
From: Christoph Hellwig @ 2026-03-23  7:11 UTC (permalink / raw)
  To: Damien Le Moal, Jens Axboe; +Cc: linux-block

Hi all,

this series adds a new option to zloop to lose data not committed to
stable storage using a flush operation on device removal.  The idea is
to help testing that file system code does the right thing in face of
volatile write caches.  For conventional devices, this can be tested
using dm-log-writes, but the concepts there don't work for sequential
write required zones.  Instead this adds an option to zloop, which
records the write pointer at the last cache flush for each zone file in
an xattr, and truncates the files down to that value on removal,
simulating losing the contents of the volatile write cache.

Changes since v2:
 - spelling fix

Changes since v1:
 - fix up the documentation

Diffstat:
 Documentation/admin-guide/blockdev/zoned_loop.rst |    5 
 drivers/block/zloop.c                             |  337 ++++++++++++++--------
 2 files changed, 226 insertions(+), 116 deletions(-)

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2026-03-23  7:12 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-18  5:53 add a "discard cache" debug option to zloop Christoph Hellwig
2026-03-18  5:53 ` [PATCH 1/2] zloop: refactor zloop_rw Christoph Hellwig
2026-03-18  6:58   ` Damien Le Moal
2026-03-18  5:53 ` [PATCH 2/2] zloop: forget write cache on force removal Christoph Hellwig
2026-03-18  7:03   ` Damien Le Moal
  -- strict thread matches above, loose matches on Subject: below --
2026-03-19  6:02 add a "discard cache" debug option to zloop v2 Christoph Hellwig
2026-03-19  6:02 ` [PATCH 1/2] zloop: refactor zloop_rw Christoph Hellwig
2026-03-19 14:06   ` Martin K. Petersen
2026-03-23  7:11 add a "discard cache" debug option to zloop v3 Christoph Hellwig
2026-03-23  7:11 ` [PATCH 1/2] zloop: refactor zloop_rw Christoph Hellwig

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox