Re: [linux-next:master] [loop] d908729e74: stress-ng.umount.ops_per_sec 100.0% regression

Mark Brown <[email protected]> Wed, 15 Jul 2026 15:57:17 +0100
Newsgroups dev.linux.lists.oe-lkp,org.kernel.vger.linux-block,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-next
Message-ID <[email protected]>
--1AbFq2Rycslg0bHG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Jul 15, 2026 at 07:30:02AM -0700, Christoph Hellwig wrote:

[Adding security maintainers for visibility.]

> 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?

Tetsuo, there was a discusion about this in the past month which seemed
to result in an agreement that you'd stop doing this and work more
closely with maintainers.  What's the story here?  It is getting to the
point where I think I have to do as Christoph suggests.  Looking at the
current contents of the tomoyo tree all I see is:

Tetsuo Handa (6):
      lib/Kconfig.debug: add CONFIG_DEBUG_AID_FOR_SYZBOT option
      net: update dev_put()/dev_hold() debugging
      net: add "struct dst_entry" debugging
      loop: Fix NULL pointer dereference in lo_rw_aio()
      kcov: fix data corruption and race conditions on PREEMPT_RT by moving saved remote state to task_struct
      apparmor: temporarily disable in syzbot kernels.

Absolutely none of which are obviously on topic for the tomoyo tree and
some of which are patches that people have previously raised concerns
with.  This is very disappointing to see.  I will check the status again
tomorrow but as things stand I think I need to drop the tomoyo
tree from -next.

To repeat the conclusion of the previous discussion you need to be
coordinating with the maintainers of other trees when adding changes for
their trees, and nobody should be adding changes not inteded for the
next merge window during the normal course of affairs.

--1AbFq2Rycslg0bHG
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmpXn8wACgkQJNaLcl1U
h9Al7gf9FtU0x/iJcY9NLYNqWXEAr+VUCoFI2q8hM4aOJBEOxbN8/SsSAe4x5Ihv
AQ4yiVyPTtlYp3ZRqPxWURMbv6Y8oX+KXP0bmMJ55frIGHhZMWDIKsGdc9NAUXLW
6gCIIaXjg3MnBlnpNJs+w5O9yVfS4x4D3zJUsZ+48XO4KHqS7a+Fdwn4NjKgwp0o
pzjQq/L+R83+qrFRu54qilL9944nR+BnXu+CZtw0cjABe8bi+TpE9c8s4hxKtJdu
t09w4U/mMe2cuDpiACgFVFLIysTdE6iyo4jodQ6UAcdTGXVU9ctf72srJtnlbQyv
rNq20dGyIIVj49izqtjhEqecXZMoNw==
=9lZA
-----END PGP SIGNATURE-----

--1AbFq2Rycslg0bHG--