public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Carlos Maiolino <cem@kernel.org>, Christoph Hellwig <hch@lst.de>,
	bfoster@redhat.com, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs: fix XFS_ERRTAG_FORCE_ZERO_RANGE for zoned file system
Date: Tue, 16 Dec 2025 18:31:29 +0100	[thread overview]
Message-ID: <20251216173129.GA14116@lst.de> (raw)
In-Reply-To: <20251216155431.GP7725@frogsfrogsfrogs>

On Tue, Dec 16, 2025 at 07:54:31AM -0800, Darrick J. Wong wrote:
> The original version is correct.  If you have 4k fsblocks and a
> zerorange request for 8GB - 2 bytes starting at 4097, you'll have to
> actually zero 4097-8191 and 8589930496 - 8589934591.  (Almost) one block
> each, at each end.
> 
> That said, "one block at each end" conveys that adquately in modern day
> English usage and people think I'm old fashioned even for uttering the
> first version. ;)
> 
> (Old fashioned being 1960s :P)

You're the only native speaker, so I'll defer to you.  A little
old-school is always good anyway.


  reply	other threads:[~2025-12-16 17:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <P_OCd7pNcLvRe038VeBLKmIi6KSgitIcPVyjn56Ucs9A34-ckTtKbjGP08W5TLKsAjB8PriOequE0_FNUOny-Q==@protonmail.internalid>
2025-12-15  6:05 ` [PATCH v2] xfs: fix XFS_ERRTAG_FORCE_ZERO_RANGE for zoned file system Christoph Hellwig
2025-12-16  8:03   ` Carlos Maiolino
2025-12-16  8:06     ` Christoph Hellwig
2025-12-16  8:11       ` Carlos Maiolino
2025-12-16 15:54         ` Darrick J. Wong
2025-12-16 17:31           ` Christoph Hellwig [this message]
2025-12-16 18:57   ` Brian Foster
2025-12-19  5:28     ` Christoph Hellwig
2025-12-19 14:01       ` Brian Foster

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=20251216173129.GA14116@lst.de \
    --to=hch@lst.de \
    --cc=bfoster@redhat.com \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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