All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Christian Brauner <brauner@kernel.org>
Cc: Tal Zussman <tz2294@columbia.edu>, Christoph Hellwig <hch@lst.de>,
	Jens Axboe <axboe@kernel.dk>, John Garry <john.garry@linux.dev>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/2] block: fail short atomic bounce bios in bio_iov_iter_bounce_write()
Date: Fri, 20 Nov 2026 17:43:09 +0100	[thread overview]
Message-ID: <20261120164309.GB32683@lst.de> (raw)
In-Reply-To: <20261120-gratwanderung-wickeln-mitkommen-1fa50bede59a@brauner>

On Fri, Nov 20, 2026 at 10:04:37AM +0100, Christian Brauner wrote:
> No objections per se, I just would like see Christoph take a look first.

No fucking idea.  As far a I can tell atomic writes are a mess and we
should not have done them in the first place.  Ask the people who
create this mess.

---end quoted text---

      reply	other threads:[~2026-11-20 16:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-08  4:24 [PATCH 0/2] block: fail short atomic bounce bios in bio_iov_iter_bounce_write() Tal Zussman
2026-11-08  4:24 ` [PATCH 1/2] block: fail a short atomic bounce " Tal Zussman
2026-11-08 17:13   ` John Garry
2026-11-09 18:27     ` Tal Zussman
2026-11-09 18:41       ` John Garry
2026-11-08  4:24 ` [PATCH 2/2] iomap: remove the atomic write length check in iomap_dio_bio_iter_one() Tal Zussman
2026-11-08 17:06   ` John Garry
2026-11-09 18:34     ` Tal Zussman
2026-11-09 18:44       ` John Garry
2026-11-09 22:46         ` Tal Zussman
2026-11-10  8:42           ` John Garry
2026-11-20  9:04 ` [PATCH 0/2] block: fail short atomic bounce bios in bio_iov_iter_bounce_write() Christian Brauner
2026-11-20 16:43   ` Christoph Hellwig [this message]

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=20261120164309.GB32683@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=john.garry@linux.dev \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=tz2294@columbia.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.