linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Christoph Hellwig <hch@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-block@vger.kernel.org
Subject: Re: [GIT PULL] block-bio_iov_iter_export
Date: Mon, 20 Oct 2025 06:21:36 -0700	[thread overview]
Message-ID: <aPY3YKzGbIKxFbl-@infradead.org> (raw)
In-Reply-To: <lyqal3mcvjwmzoxltydw2aoyhjllwcvv5ix2axpw24kh2iotkx@lygocjo66enh>

On Mon, Oct 20, 2025 at 08:56:59AM -0400, Kent Overstreet wrote:
> The implementation has morphed given multipage bvecs and iov_iters, but
> otherwise it looks structurally much the same as the version I
> originally introduced.

Not a pissing context, but I introduced it.  I attributed the git
authorship you because it fundamentally it based on your idea but with a
lot of tweaks.  I and many others do this to give proper credit.

> Please attribute correctly, and that would've included CCing me on the
> patch that dropped the EXPORT_SYMBOL().

No, we don't Cc the author of each line of code or even function.  The
relevant maintainer here is Jens.

> The way you're doing it with bdev_logical_block_size() is just wrong -
> even for single device filesystems! - because it's the filesystem
> blocksize that's relevant here and that isn't necessarily going to match
> (even if it matched when the filesystem was formatted, filesystems can
> be moved to different block devices).

I'm not sure what you are talking about, but the changes you seem to
be complaining about are making the alignment boundary a caller provided
argument.  Which seems to be what you're arguing for here?  Either way
this is the wrong venue.  If you want to change something sent patches
following the usual guidelines to the maintainer.


  reply	other threads:[~2025-10-20 13:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ov54jszhism7mbeu74vtyoysxnx3y3tsjbj5esszlrx3edq77s@j2vtyy45gsna>
2025-10-17  6:13 ` [GIT PULL] block-bio_iov_iter_export Christoph Hellwig
2025-10-17 13:31   ` Kent Overstreet
2025-10-20  9:35     ` Christoph Hellwig
2025-10-20 12:56       ` Kent Overstreet
2025-10-20 13:21         ` Christoph Hellwig [this message]
2025-10-20 14:49           ` Kent Overstreet
2025-10-20 14:54             ` Christoph Hellwig
2025-10-20 16:42               ` Kent Overstreet
2025-10-20 15:13             ` Greg Kroah-Hartman

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=aPY3YKzGbIKxFbl-@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=gregkh@linuxfoundation.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).