From: Christoph Hellwig <hch@infradead.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Christoph Hellwig <hch@infradead.org>,
kernel test robot <oliver.sang@intel.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
linux-next@vger.kernel.org, axboe@kernel.dk
Subject: Re: [linux-next:master] [loop] d908729e74: stress-ng.umount.ops_per_sec 100.0% regression
Date: Wed, 15 Jul 2026 07:53:25 -0700 [thread overview]
Message-ID: <alee5QMFtyPeqVKR@infradead.org> (raw)
In-Reply-To: <4ea4703c-7385-4f75-aee2-f21a6c8cce82@I-love.SAKURA.ne.jp>
On Wed, Jul 15, 2026 at 11:45:41PM +0900, Tetsuo Handa wrote:
> On 2026/07/15 23:30, Christoph Hellwig wrote:
> > It's also a patch that has never been added to the maintainer
> > tree for goot reson. Tetsuo keeps doing this, so can we please
> > stop including their trees in linux-next as there seems to be
> > no other way to stop this?
>
> Then, can we please keep discussion on
> https://syzkaller.appspot.com/bug?extid=cd8a9a308e879a4e2c28 alive?
> I am asking Al Viro to reproduce xfs/259 problem, but it seems that
> Al is too busy to respond. I can drop this patch if somebody is
> interested in fixing this bug which became visible in 7.1. Current
> state is a result of insufficient interests/resources for debugging.
Not my business. But adding random patches affecting other subsystems
without any buy in is a no-go. Doing this repeatedly after beeing
reminded not to do it and for multiple subsystems is a red flag.
next prev parent reply other threads:[~2026-07-15 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 13:55 [linux-next:master] [loop] d908729e74: stress-ng.umount.ops_per_sec 100.0% regression kernel test robot
2026-07-15 14:25 ` Tetsuo Handa
2026-07-15 14:30 ` Christoph Hellwig
2026-07-15 14:45 ` Tetsuo Handa
2026-07-15 14:53 ` Christoph Hellwig [this message]
2026-07-15 16:02 ` Mark Brown
2026-07-15 14:57 ` Mark Brown
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=alee5QMFtyPeqVKR@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=broonie@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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.