From: Pavel Begunkov <[email protected]>
To: Christoph Hellwig <[email protected]>, Jens Axboe <[email protected]>
Cc: Christian Brauner <[email protected]>,
[email protected], Dave Chinner <[email protected]>,
[email protected], "Darrick J . Wong" <[email protected]>,
[email protected], wu lei <[email protected]>
Subject: Re: [PATCH v2 1/1] iomap: propagate nowait to block layer
Date: Wed, 5 Mar 2025 00:18:12 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 3/5/25 00:14, Pavel Begunkov wrote:
> On 3/4/25 23:49, Christoph Hellwig wrote:
>> On Tue, Mar 04, 2025 at 04:43:29PM -0700, Jens Axboe wrote:
>>> On 3/4/25 4:26 PM, Christoph Hellwig wrote:
>>>> On Tue, Mar 04, 2025 at 10:36:16AM -0700, Jens Axboe wrote:
>>>>> stable and actual production certainly do. Not that this should drive
>>>>> upstream development in any way, it's entirely unrelated to the problem
>>>>> at hand.
>>>>
>>>> And that's exactly what I'm saying. Do the right thing instead of
>>>> whining about backports to old kernels.
>>>
>>> Yep we agree on that, that's obvious. What I'm objecting to is your
>>> delivery, which was personal rather than factual, which you should imho
>>> apologize for.
>>
>> I thus sincerly apologize for flaming Pavel for whining about
>
> Again, pretty interesting choice of words, because it was more akin
> to a tantrum. I hope you don't think you'd be taken seriously after
> that, I can't, and not only from this conversation.
>
>> backporting, but I'd still prefer he would have taken up that proposal
>> on technical grounds as I see absolutely no alternatively to
>> synchronously returning an error.
>
> The "You have to do X" hardly reveals any details to claim "technical
> grounds". Take stable out of the question, and I would still think
> that a simple understandable fix for upstream is better than jumping
> to a major rework right away.
That is _if_ there is a simple fix, but your argument was that
it's "not very accurate", which is not very useful.
>>> And honestly pretty tiring that this needs to be said, still. Really.
>>
>> An I'm really tired of folks whining about backporting instead of
>> staying ontopic.
--
Pavel Begunkov
next prev parent reply other threads:[~2025-03-05 0:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 12:18 [PATCH v2 1/1] iomap: propagate nowait to block layer Pavel Begunkov
2025-03-04 16:07 ` Christoph Hellwig
2025-03-04 16:41 ` Pavel Begunkov
2025-03-04 16:59 ` Christoph Hellwig
2025-03-04 17:36 ` Jens Axboe
2025-03-04 23:26 ` Christoph Hellwig
2025-03-04 23:43 ` Jens Axboe
2025-03-04 23:49 ` Christoph Hellwig
2025-03-05 0:14 ` Pavel Begunkov
2025-03-05 0:18 ` Pavel Begunkov [this message]
2025-03-04 17:54 ` Pavel Begunkov
2025-03-04 23:28 ` Christoph Hellwig
2025-03-04 19:22 ` Darrick J. Wong
2025-03-04 20:35 ` Pavel Begunkov
2025-03-05 0:01 ` Christoph Hellwig
2025-03-05 0:45 ` Pavel Begunkov
2025-03-05 1:34 ` Christoph Hellwig
2025-03-04 21:11 ` Dave Chinner
2025-03-04 22:47 ` Pavel Begunkov
2025-03-04 23:40 ` Christoph Hellwig
2025-03-05 1:19 ` Dave Chinner
2025-03-05 14:10 ` Christoph Hellwig
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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