Re: Policy regarding linux-next only changes

On 2026/07/23 2:47, Theodore Tso wrote:
> On Thu, Jul 23, 2026 at 12:07:44AM -0500, Tetsuo Handa wrote:
>> The procedural problem is that developers / maintainers are too busy
>> to respond to my debug patches. Since I am debugging difficult bugs
>> where nobody else are willing to spend resources, this is an
>> expected result. I am OK to post my debug patches to ML. But without
>> responses / interests from developers / maintainers, this problem
>> won't be able to make progress.
>>
>> Just saying "Not my business." is not helpful.
> 
> Is what is happening that when your security LSM (Tomoyo) is enabled,
> this causes lockdep or warnings or other issues in other subsystems?

No. Problems are not related to tomoyo.

What is happening is that I am using tomoyo git tree as a hook for
executing debug printk() (using linux-next git tree) in order to debug
problems which syzbot has found but nobody can afford looking into.

Individual git tree is not served as a hook for applying debug patches
like "quilt push"; one of reasons is that "git" (compared to "quilt") is
not intended for removing a patch when that patch became no longer
necessary (due to problem being fixed).