public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Fabio Fantoni <fantonifabio@tiscali.it>
Cc: linux-block@vger.kernel.org, axboe@kernel.dk,
	Christoph Hellwig <hch@infradead.org>,
	Sergei Shtepa <sergei.shtepa@veeam.com>
Subject: Re: blksnap: no feedback received on latest patchset - any concerns?
Date: Thu, 19 Mar 2026 09:16:52 -0700	[thread overview]
Message-ID: <abwhdNB-j6GOQGRv@infradead.org> (raw)
In-Reply-To: <5459ee8c-075f-453f-8999-19219f9a6fdc@tiscali.it>

Hi Fabio,

a 2 year old patchset has been paged out of everyones mind.  I still
think functionality like it would be useful, but it needs to be resend
to get fresh eyes.

On Thu, Mar 19, 2026 at 01:06:10PM +0100, Fabio Fantoni wrote:
> Hi Jens, hi all,
> 
> The blksnap v7 patchset was posted in February 2024 and has received no
> response so far. As someone who has followed this project closely, I wanted
> to ask directly: is there a reason this patchset is not being considered?
> 
> This is a module for non-persistent block device snapshots, useful for
> backup on filesystems like ext4 that don't have their own snapshot
> mechanism. It went through 7 revision cycles with review of some people and
> substantial contributions from Christoph Hellwig. The amount of work that
> Sergei Shtepa and Christoph put into this has been remarkable.
> 
> The silence after v7 seems to have led the developer to abandon the upstream
> effort entirely, which is unfortunate because seems to me there's still a
> need for a block-level snapshot capabilities module integrated upstream, or
> am I wrong?
> 
> I fully understand if there are technical objections, but could you please
> share what they are? Even a definitive rejection, accompanied by clear
> reasoning, would help the community understand whether it’s better to take a
> different approach or address specific concerns in similar cases.
> 
> Thank you for your time.
> 
---end quoted text---

  reply	other threads:[~2026-03-19 16:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19 12:06 blksnap: no feedback received on latest patchset - any concerns? Fabio Fantoni
2026-03-19 16:16 ` Christoph Hellwig [this message]
2026-03-19 16:24   ` 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=abwhdNB-j6GOQGRv@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=fantonifabio@tiscali.it \
    --cc=linux-block@vger.kernel.org \
    --cc=sergei.shtepa@veeam.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