Re: Policy regarding linux-next only changes

[Theodore Tso]

On Sat, Jul 25, 2026 at 12:29:27AM -0500, Tetsuo Handa wrote:
> The problem is that a maintainer who has the permission to
> accept/reject patches tends to become defunctional when syzbot is
> involved. What actions can the Linux kernel community take in order
> to address this problem (instead of just ignoring developers who are
> trying to fix bugs)?

Fundamentally, not all bugs are worth fixing.  And if you believe that
all bugs are worth fixing, you need to convince companies to **fund**
that work, and not leave it as unfunded mandate.  If you give me some
minions who can be dedicated to help fix bugs, I'm certainly willing
to provide technical direction.  But there's no such thing as a free
lunch --- and the business case is not as clear cut as you seem to be
assuming.

In essence, this is a cost allocation problem.  When you ask for help
from other maintainers to fix something that you care about, if it's
not important to them or their company / management chain, you are
dumping costs from you to them.  This can work if you can also help
them in turn in other areas.  This happens all the time, actually, and
it's what makes Open Source work.

So I think the way we solve this problem is by finding ways to
allocate the costs to those companies or organizations that think it
is a good fit for their business, and to reduce the burden on those
whose company (or management chain) doesn't think the business case is
sufficiently compelling.

Other solutions might include finding some AI solution which can
filter the low-priority quality Syzbot reports from the high-quality
ones.  If some companies or some departments may have different
priorities, perhaps they can use different filuters, so they can work
on those bugs that they think are important.

Perhaps AI's can do a better job at proposing some patches that
resolve the problem, or creating reliable reproducers that don't
require thousands of VM hours of testing.

One of the reasons why I am personally more supportive about Sashiko
than syzbot is because Sashiko is a technology which is reducing *my*
workload.  It does transfer more work to the contributor, but if they
are trying to get code into the kernel and if their company think
there is a business case for that new feature, it seems right that we
require that pay the development costs of submitting high-quality
code.

Cheeres,

					- Ted