From: Kent Overstreet <kent.overstreet@linux.dev>
To: Christoph Hellwig <hch@lst.de>
Cc: Theodore Ts'o <tytso@mit.edu>,
Shuah Khan <skhan@linuxfoundation.org>,
Michal Hocko <mhocko@suse.com>,
Dave Chinner <david@fromorbit.com>,
Andrew Morton <akpm@linux-foundation.org>,
Yafang Shao <laoar.shao@gmail.com>,
jack@suse.cz, Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-bcachefs@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
"conduct@kernel.org" <conduct@kernel.org>
Subject: Re: [PATCH 1/2 v2] bcachefs: do not use PF_MEMALLOC_NORECLAIM
Date: Wed, 20 Nov 2024 23:53:24 -0500 [thread overview]
Message-ID: <thwbzrybt6kk3x6o5ege3h7k6vsip4j6mllxdvn6poldvdczz6@zobwlfwgxhkt> (raw)
In-Reply-To: <20241121042558.GA20176@lst.de>
On Thu, Nov 21, 2024 at 05:25:58AM +0100, Christoph Hellwig wrote:
> On Wed, Nov 20, 2024 at 03:47:59PM -0800, Theodore Ts'o wrote:
> > On Wed, Nov 20, 2024 at 05:55:03PM -0500, Kent Overstreet wrote:
> > > Shuah, would you be willing to entertain the notion of modifying your...
> >
> > Kent, I'd like to gently remind you that Shuah is not speaking in her
> > personal capacity, but as a representative of the Code of Conduct
> > Committee[1], as she has noted in her signature. The Code of Conduct
> > Committee is appointed by, and reports to, the TAB[2], which is an
> > elected body composed of kernel developers and maintainers.
>
> FYI, without taking any stance on the issue under debate here, I find the
> language used by Shuah on behalf of the Code of Conduct committee
> extremely patronising and passive aggressive. This might be because I
> do not have an American academic class background, but I would suggest
> that the code of conduct committee should educate itself about
> communicating without projecting this implicit cultural and class bias
> so blatantly.
I wasn't even thinking about the language issue, but I think that's a
very good point.
We have a very strong culture of personal responsibility and taking
responsibility for our work here, and I think that's one of the main
thing that enables us to function and work together even when we're
constantly butting heads.
Broadly speaking, what that means to me is: I will justify, explain and
give the reasoning for my actions if asked, and if I can't because I
made a mistake, then I will make it right or at least acknowledge my
mistake.
So, the very passive language from Shuah (i.e. "I'm not the one 'doing'
this, I'm just implementing the policy that we all decided on, even
though I totally wrote and advocated for that policy") does seem
problematic to me as well.
next prev parent reply other threads:[~2024-11-21 4:53 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 8:47 [PATCH 0/2] get rid of PF_MEMALLOC_NORECLAIM Michal Hocko
2024-08-26 8:47 ` [PATCH 1/2] bcachefs: do not use PF_MEMALLOC_NORECLAIM Michal Hocko
2024-08-26 13:11 ` Matthew Wilcox
2024-08-26 16:48 ` Michal Hocko
2024-08-26 19:39 ` Kent Overstreet
2024-08-26 19:41 ` Matthew Wilcox
2024-08-26 19:42 ` Kent Overstreet
2024-08-26 19:47 ` Matthew Wilcox
2024-08-26 19:54 ` Kent Overstreet
2024-08-26 19:44 ` Kent Overstreet
2024-08-26 19:58 ` Michal Hocko
2024-08-26 20:00 ` Kent Overstreet
2024-08-26 20:27 ` Michal Hocko
2024-08-26 20:43 ` Kent Overstreet
2024-08-26 21:10 ` Kent Overstreet
2024-08-27 6:01 ` Michal Hocko
2024-08-27 6:40 ` Kent Overstreet
2024-08-27 6:58 ` Michal Hocko
2024-08-27 7:05 ` Kent Overstreet
2024-08-27 7:35 ` Michal Hocko
2024-08-26 19:52 ` kernel test robot
2024-08-26 20:53 ` kernel test robot
2024-08-27 2:23 ` kernel test robot
2024-08-27 6:15 ` [PATCH 1/2 v2] " Michal Hocko
2024-08-27 12:29 ` Christoph Hellwig
2024-08-28 4:09 ` Dave Chinner
2024-08-29 10:02 ` Kent Overstreet
2024-08-29 13:12 ` Dave Chinner
2024-08-29 13:22 ` Kent Overstreet
2024-08-29 13:32 ` Kent Overstreet
2024-08-29 14:03 ` Yafang Shao
2024-09-02 0:23 ` Dave Chinner
2024-09-02 1:35 ` Kent Overstreet
2024-09-02 8:41 ` Michal Hocko
2024-09-02 8:52 ` Kent Overstreet
2024-09-02 9:39 ` Michal Hocko
2024-09-02 9:51 ` Kent Overstreet
2024-09-02 14:07 ` Jonathan Corbet
2024-09-04 18:01 ` Shuah Khan
2024-11-20 20:34 ` Kent Overstreet
2024-11-20 21:12 ` Shuah Khan
2024-11-20 21:20 ` Kent Overstreet
2024-11-20 21:37 ` Shuah Khan
2024-11-20 22:21 ` Shuah Khan
2024-11-20 22:39 ` Kent Overstreet
2024-11-20 22:55 ` Kent Overstreet
2024-11-20 23:21 ` Kent Overstreet
2024-11-20 23:47 ` Theodore Ts'o
2024-11-20 23:57 ` Kent Overstreet
2024-11-21 0:10 ` Kent Overstreet
2024-11-21 4:25 ` Christoph Hellwig
2024-11-21 4:53 ` Kent Overstreet [this message]
2024-11-21 23:53 ` Shuah Khan
2024-11-22 6:51 ` Kent Overstreet
2024-11-22 12:06 ` Christoph Hellwig
2024-11-21 21:32 ` Martin Steigerwald
2024-11-22 9:47 ` Geert Uytterhoeven
2024-11-21 5:51 ` Kent Overstreet
2024-11-21 8:43 ` review process (was: underalated stuff) Michal Hocko
2024-11-21 9:03 ` Kent Overstreet
2024-11-21 20:17 ` [PATCH 1/2 v2] bcachefs: do not use PF_MEMALLOC_NORECLAIM Simona Vetter
2024-11-21 21:26 ` Martin Steigerwald
2024-11-22 21:48 ` Dan Williams
2024-11-22 22:02 ` Kent Overstreet
2024-08-29 9:37 ` [PATCH 1/2] " Jan Kara
2024-08-26 8:47 ` [PATCH 2/2] mm: drop PF_MEMALLOC_NORECLAIM Michal Hocko
2024-08-26 13:48 ` Yafang Shao
2024-08-26 16:54 ` Michal Hocko
2024-08-26 13:59 ` Matthew Wilcox
2024-08-26 16:51 ` Michal Hocko
2024-08-26 17:49 ` Matthew Wilcox
2024-08-26 19:18 ` Michal Hocko
2024-08-26 19:20 ` Matthew Wilcox
2024-08-28 4:11 ` Dave Chinner
2024-08-29 21:45 ` Vlastimil Babka
2024-08-26 19:04 ` Kent Overstreet
2024-08-27 12:29 ` Christoph Hellwig
2025-10-01 11:29 [PATCH 1/2 v2] bcachefs: do not use PF_MEMALLOC_NORECLAIM Stephen Whitten
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=thwbzrybt6kk3x6o5ege3h7k6vsip4j6mllxdvn6poldvdczz6@zobwlfwgxhkt \
--to=kent.overstreet@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=conduct@kernel.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jmorris@namei.org \
--cc=laoar.shao@gmail.com \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=skhan@linuxfoundation.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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