From: Greg KH <gregkh@linuxfoundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>, Chun Ng <chunn@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Ankita Garg <ankitag@nvidia.com>
Subject: Re: [REGRESSION]: mmap performance regression starting with k-6.1
Date: Fri, 24 Nov 2023 15:13:58 +0000 [thread overview]
Message-ID: <2023112421-many-jaybird-6200@gregkh> (raw)
In-Reply-To: <ZWC8BOtPW2bWBFqh@casper.infradead.org>
On Fri, Nov 24, 2023 at 03:06:44PM +0000, Matthew Wilcox wrote:
> On Fri, Nov 24, 2023 at 11:52:06AM +0000, Greg KH wrote:
> > On Fri, Nov 24, 2023 at 01:04:28AM +0000, Matthew Wilcox wrote:
> > > On Fri, Nov 24, 2023 at 07:15:34AM +0700, Bagas Sanjaya wrote:
> > > > On Thu, Nov 23, 2023 at 03:38:18PM +0000, Matthew Wilcox wrote:
> > > > > On Thu, Nov 23, 2023 at 12:07:40PM +0700, Bagas Sanjaya wrote:
> > > > > > Anyway, I'm adding this regression to regzbot:
> > > > > >
> > > > > > #regzbot ^introduced: v6.0..v6.1
> > > > >
> > > > > this is not a regression. close it, you idiot.
> > > > >
> > > > >
> > > >
> > > > why?
> > > >
> > > > Confused...
> > >
> > > yes. you're perpetually confused. stop trying to help, you only make
> > > things worse. learn about the things you work on, or give up.
> >
> > Um, is this really called for? Bagas is trying to help track
> > regressions, and if something isn't a regression like you say here, a
> > simple "This is not a regression, it's already resolved in newer
> > kernels" is fine.
>
> Bagas has a long history of inappropriately attempting to "help" and due
> to a lack of understanding wasting peoples time. He's not too dissimilar
> to the various wrongbots we've had over the years, including Richard B
> Johnson, Markus Elfring, etc. I've tried to help guide him towards being
> a more productive contributor, but'have failed. Mostly I ignore him now,
> but when he's instructing a bot to harass me, that crosses a line.
Nope, still not justification to lash out at an individual, sorry.
Please be more careful, and kind, in the future.
greg k-h
next prev parent reply other threads:[~2023-11-24 15:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 20:03 [REGRESSION]: mmap performance regression starting with k-6.1 Chun Ng
2023-11-23 1:18 ` Bagas Sanjaya
2023-11-23 3:06 ` Chun Ng
2023-11-23 5:01 ` Bagas Sanjaya
2023-11-23 5:07 ` Bagas Sanjaya
2023-11-23 8:29 ` David Wang
2023-11-23 14:34 ` Liam R. Howlett
2023-11-24 5:08 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-11-26 7:18 ` David Wang
2023-11-26 13:47 ` Matthew Wilcox
2023-11-23 15:38 ` Matthew Wilcox
2023-11-24 0:15 ` Bagas Sanjaya
2023-11-24 1:04 ` Matthew Wilcox
2023-11-24 11:52 ` Greg KH
2023-11-24 15:06 ` Matthew Wilcox
2023-11-24 15:13 ` Greg KH [this message]
2023-11-24 15:29 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-25 1:50 ` Chun Ng
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=2023112421-many-jaybird-6200@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=ankitag@nvidia.com \
--cc=bagasdotme@gmail.com \
--cc=chunn@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=regressions@lists.linux.dev \
--cc=willy@infradead.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 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.