From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Eric Sandeen <sandeen@sandeen.net>,
Steven Rostedt <rostedt@goodmis.org>,
Guenter Roeck <linux@roeck-us.net>,
Christoph Hellwig <hch@infradead.org>,
ksummit@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: Re: [MAINTAINERS/KERNEL SUMMIT] Trust and maintenance of file systems
Date: Tue, 19 Sep 2023 12:57:56 -0400 [thread overview]
Message-ID: <4b2f3646fb3da593ec67c47bcfaec3b0a744dc5b.camel@HansenPartnership.com> (raw)
In-Reply-To: <ZQkK8kTPhFw8BpVA@dread.disaster.area>
On Tue, 2023-09-19 at 12:44 +1000, Dave Chinner wrote:
> On Sat, Sep 16, 2023 at 05:50:50PM -0400, James Bottomley wrote:
> > On Sat, 2023-09-16 at 08:48 +1000, Dave Chinner wrote:
> > > On Wed, Sep 13, 2023 at 10:03:55AM -0700, Linus Torvalds wrote:
> > [...]
> > > > - "they use the buffer cache".
> > > >
> > > > Waah, waah, waah.
> > >
> > > .... you dismiss those concerns in the same way a 6 year old
> > > school yard bully taunts his suffering victims.
> > >
> > > Regardless of the merits of the observation you've made, the tone
> > > and content of this response is *completely unacceptable*.
> > > Please keep to technical arguments, Linus, because this sort of
> > > response has no merit what-so-ever. All it does is shut down the
> > > technical discussion because no-one wants to be the target of
> > > this sort of ugly abuse just for participating in a technical
> > > discussion.
> > >
> > > Given the number of top level maintainers that signed off on the
> > > CoC that are present in this forum, I had an expectation that
> > > this is a forum where bad behaviour is not tolerated at all. So
> > > I've waited a couple of days to see if anyone in a project
> > > leadership position is going to say something about this
> > > comment.....
> > >
> > > <silence>
> > >
> > > The deafening silence of tacit acceptance is far more damning
> > > than the high pitched squeal of Linus's childish taunts.
> >
> > Well, let's face it: it's a pretty low level taunt and it wasn't
> > aimed at you (or indeed anyone on the thread that I could find) and
> > it was backed by technical argument in the next sentence. We all
> > have a tendency to let off steam about stuff in general not at
> > people in particular as you did here:
> >
> > https://lore.kernel.org/ksummit/ZP+vcgAOyfqWPcXT@dread.disaster.area/
>
> There's a massive difference between someone saying no to a wild
> proposal with the backing of solid ethical arguments against
> experimentation on non-consenting human subjects vs someone calling
> anyone who might disagree with them a bunch of cry-babies.
>
> You do yourself a real disservice by claiming these two comments are
> in any way equivalent.
Well, let's see shall we. The detrimental impact of an email often
results from the first sentence which is what most people see and react
to especially on the modern display devices like phones. Pretty much
as you reacted to the first sentence from Linus above. Your first
sentence in the email I quoted above replying to my idea was:
> No fucking way.
Absent further context that's a textbook stress inducing personal
attack. Now, I've been on the receiving end of things like this for a
long time, so I simply deployed the usual stress reduction techniques,
read the rest of your email, deleted the knee jerk response and waited
to see if anyone else had a different opinion.
However, the key point is that your email induced the same stress
reaction in me that Linus' statement apparently did in you, so
absolutely I see an equivalence.
> > But I didn't take it as anything more than a rant about AI in
> > general and syzbot in particular and certainly I didn't assume it
> > was aimed at me or anyone else.
>
> I wasn't ranting about AI at all. If you think that was what I was
> talking about then you have, once again, completely missed the
> point.
>
> I was talking about the *ethics of our current situation* and how
> that should dictate the behaviour of community members and bots that
> they run for the benefit of the community. If a bot is causing harm
> to the community, then ethics dictates that there is only one
> reasonable course of action that can be taken...
>
> This has *nothing to do with AI* and everything to do with how the
> community polices hostile actors in the community. If 3rd party
> run infrastructure is causing direct harm to developers and they
> aren't allowed to opt out, then what do we do about it?
My point was basically trying to improve the current situation by
getting the AI processes producing the reports to make them more useful
and eliminate a significant portion of the outbound flow, but I get
that some people are beyond that and would go for amputation rather
than attempted cure.
> > If everyone reached for the code of conduct when someone had a non-
> > specific rant using colourful phraseology, we'd be knee deep in
> > complaints, which is why we tend to be more circumspect when it
> > happens.
>
> I disagree entirely, and I think this a really bad precedent to try
> to set. Maybe you see it as "Fred has a colourful way with words",
> but that doesn't change the fact the person receiving that comment
> might see the same comment very, very differently.
Which was precisely my point about your email above. At its most basic
level the standard you hold yourself to has to be the same or better
than the standard you hold others to.
James
> I don't think anyone can dispute the fact that top level kernel
> maintainers are repeat offenders when it comes to being nasty,
> obnoxious and/or abusive. Just because kernel maintainers have
> normalised this behaviour between themselves, it does not make it OK
> to treat anyone else this way.
>
> Maintainers need to be held to a higher standard than the rest of
> the community - the project leaders need to set the example of how
> everyone else should behave, work and act - and right now I am _very
> disappointed_ by where this thread has ended up.
next prev parent reply other threads:[~2023-09-19 16:58 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 14:07 [MAINTAINERS/KERNEL SUMMIT] Trust and maintenance of file systems Christoph Hellwig
2023-09-05 23:06 ` Dave Chinner
2023-09-05 23:23 ` Matthew Wilcox
2023-09-06 2:09 ` Dave Chinner
2023-09-06 15:06 ` Christian Brauner
2023-09-06 15:59 ` Christian Brauner
2023-09-06 19:09 ` Geert Uytterhoeven
2023-09-08 8:34 ` Christoph Hellwig
2023-09-07 0:46 ` Bagas Sanjaya
2023-09-09 12:50 ` James Bottomley
2023-09-09 15:44 ` Matthew Wilcox
2023-09-10 19:51 ` James Bottomley
2023-09-10 20:19 ` Kent Overstreet
2023-09-10 21:15 ` Guenter Roeck
2023-09-11 3:10 ` Theodore Ts'o
2023-09-11 19:03 ` James Bottomley
2023-09-12 0:23 ` Dave Chinner
2023-09-12 16:52 ` H. Peter Anvin
2023-09-09 22:42 ` Kent Overstreet
2023-09-10 8:19 ` Geert Uytterhoeven
2023-09-10 8:37 ` Bernd Schubert
2023-09-10 16:35 ` Kent Overstreet
2023-09-10 17:26 ` Geert Uytterhoeven
2023-09-10 17:35 ` Kent Overstreet
2023-09-11 1:05 ` Dave Chinner
2023-09-11 1:29 ` Kent Overstreet
2023-09-11 2:07 ` Dave Chinner
2023-09-11 13:35 ` David Disseldorp
2023-09-11 17:45 ` Bart Van Assche
2023-09-11 19:11 ` David Disseldorp
2023-09-11 23:05 ` Dave Chinner
2023-09-26 5:24 ` Eric W. Biederman
2023-09-08 8:55 ` Christoph Hellwig
2023-09-08 22:47 ` Dave Chinner
2023-09-06 22:32 ` Guenter Roeck
2023-09-06 22:54 ` Dave Chinner
2023-09-07 0:53 ` Bagas Sanjaya
2023-09-07 3:14 ` Dave Chinner
2023-09-07 1:53 ` Steven Rostedt
2023-09-07 2:22 ` Dave Chinner
2023-09-07 2:51 ` Steven Rostedt
2023-09-07 3:26 ` Matthew Wilcox
2023-09-07 8:04 ` Thorsten Leemhuis
2023-09-07 10:29 ` Christian Brauner
2023-09-07 11:18 ` Thorsten Leemhuis
2023-09-07 12:04 ` Matthew Wilcox
2023-09-07 12:57 ` Guenter Roeck
2023-09-07 13:56 ` Christian Brauner
2023-09-08 8:44 ` Christoph Hellwig
2023-09-07 3:38 ` Dave Chinner
2023-09-07 11:18 ` Steven Rostedt
2023-09-13 16:43 ` Eric Sandeen
2023-09-13 16:58 ` Guenter Roeck
2023-09-13 17:03 ` Linus Torvalds
2023-09-15 22:48 ` Dave Chinner
2023-09-16 19:44 ` Steven Rostedt
2023-09-16 21:50 ` James Bottomley
2023-09-17 1:40 ` NeilBrown
2023-09-17 17:30 ` Linus Torvalds
2023-09-17 18:09 ` Linus Torvalds
2023-09-17 18:57 ` Theodore Ts'o
2023-09-17 19:45 ` Linus Torvalds
2023-09-18 11:14 ` Jan Kara
2023-09-18 17:26 ` Linus Torvalds
2023-09-18 19:32 ` Jiri Kosina
2023-09-18 19:59 ` Linus Torvalds
2023-09-18 20:50 ` Theodore Ts'o
2023-09-18 22:48 ` Linus Torvalds
2023-09-18 20:33 ` H. Peter Anvin
2023-09-19 4:56 ` Dave Chinner
2023-09-25 9:43 ` Christoph Hellwig
2023-09-27 22:23 ` Dave Kleikamp
2023-09-19 1:15 ` Dave Chinner
2023-09-19 5:17 ` Matthew Wilcox
2023-09-19 16:34 ` Theodore Ts'o
2023-09-19 16:45 ` Matthew Wilcox
2023-09-19 17:15 ` Linus Torvalds
2023-09-19 22:57 ` Dave Chinner
2023-09-18 14:54 ` Bill O'Donnell
2023-09-19 2:44 ` Dave Chinner
2023-09-19 16:57 ` James Bottomley [this message]
2023-09-25 9:38 ` Christoph Hellwig
2023-09-25 14:14 ` Dan Carpenter
2023-09-25 16:50 ` Linus Torvalds
2023-09-07 9:48 ` Dan Carpenter
2023-09-07 11:04 ` Segher Boessenkool
2023-09-07 11:22 ` Steven Rostedt
2023-09-07 12:24 ` Segher Boessenkool
2023-09-07 11:23 ` Dan Carpenter
2023-09-07 12:30 ` Segher Boessenkool
2023-09-12 9:50 ` Richard Biener
2023-10-23 5:19 ` Eric Gallager
2023-09-08 8:39 ` Christoph Hellwig
2023-09-08 8:38 ` Christoph Hellwig
2023-09-08 23:21 ` Dave Chinner
2023-09-07 0:48 ` Bagas Sanjaya
2023-09-07 3:07 ` Guenter Roeck
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=4b2f3646fb3da593ec67c47bcfaec3b0a744dc5b.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=ksummit@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rostedt@goodmis.org \
--cc=sandeen@sandeen.net \
--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).