From: Mike Snitzer <snitzer@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: dm-devel@lists.linux.dev, Mikulas Patocka <mpatocka@redhat.com>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: dm-flakey: Fix memory corruption
Date: Sun, 9 Mar 2025 11:44:38 -0400 [thread overview]
Message-ID: <Z823ZmamUoGO8P6I@kernel.org> (raw)
In-Reply-To: <ij3pre7rlgez3ybsfrsj2i3ohoeb5ma5rgz3tfuv63h7rv6uoo@2hw6452r4qbn>
On Sat, Mar 08, 2025 at 04:50:05PM -0500, Kent Overstreet wrote:
> On Sat, Mar 08, 2025 at 01:19:30PM -0500, Mike Snitzer wrote:
> > On Sat, Mar 08, 2025 at 10:50:08AM -0500, Kent Overstreet wrote:
> > > So, this code clearly isn't getting tested - at all. Besides this bug,
> > > the parsing for the "corrupt" modes is also broken.
> > >
> > > Guys, don't push broken crap, and figure out how to write some tests.
> >
> > Thank you sir, may we have another?
> >
> > Like you never introduced a bug in your life?
> >
> > Not going to tolerate your entitled primadonna attitude here. You are
> > capable of being better, you've chosen not to be on this issue (twice)
>
> Talking about basic engineering standards is in no way "being a prima
> donna". Testing your changes is as basic as it gets, and this code
> wasn't tested _at all_.
"entitled primadonna attitude" was me pulling punches.
I don't disagree that this is a bug that was missed and that proper
testing hasn't been performed (I'd quibble with the no testing part
only because I cannot speak for Mikulas and don't like to assume I
know it all).
But you're missing the very problematic detail: you used a bug in an
optional feature of the test-only dm-flakey target to try to take a
pound of flesh while preaching from your high horse. That is
unacceptable behaviour that won't be tolerated here. Be cool and
others will be in return (unless you keep setting fire to bridges).
Fin.
next prev parent reply other threads:[~2025-03-09 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 15:50 [PATCH] dm-flakey: Fix memory corruption Kent Overstreet
2025-03-08 18:19 ` Mike Snitzer
2025-03-08 21:50 ` Kent Overstreet
2025-03-09 15:44 ` Mike Snitzer [this message]
2025-03-09 17:04 ` Bring back md-faulty? (was Re: dm-flakey: Fix memory corruption) Kent Overstreet
2025-03-10 1:13 ` Mike Snitzer
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=Z823ZmamUoGO8P6I@kernel.org \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=kent.overstreet@linux.dev \
--cc=mpatocka@redhat.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 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.