Re: [linux-next:master] [loop] d908729e74: stress-ng.umount.ops_per_sec 100.0% regression
Christoph Hellwig <[email protected]> Wed, 15 Jul 2026 07:53:25 -0700
| 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]> |
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.