Re: [PATCH] mm/khugepaged: reject shmem collapse ranges beyond i_size

["David Hildenbrand (Arm)" <david@kernel.org>]

>> Posting preexisting stuff to the mailing list is not great, at least
>> not right now.
> 
> Yet I've been explicitly asked about it by others. So at least there are
> various opinions here.

I suspect these other subsystems are not as exposed to Anthropic's long list of
fixes :)

> 
>> We were very happy that preexisting issues went into the private bugtracker. I
>> want to delegate stuff to people in my team to screen them and see if it needs
>> fixing. Well controlled.
>>
>> Now either:
>>
>> (a) it was never really gone, and we were in disbelieve that preexisting issues
>>     are no longer posted publicly.
>>
>> (b) Sashiko maintainer decided to re-enable it without consulting us.
> 
> The correct version is b*, it's indeed back, but in a completely
> reworked way, as I wrote to Lorenzo yesterday.
> 
> Pre-existing reports are now limited to the first non-rfc version of the
> patchset, they are limited in numbers per patch (1-2), they are
> _deduplicated and posted strictly once per issue_.
> 
> Re consulting the problem is that there are several hundreds maintainers
> with drastically different views. If we'll wait for everybody's agreement
> each time, nothing will ever move. So I have to make some decisions like
> this on my own. And, yes, some of them will be wrong or not perfect.
> I do fix/adjust things constantly. But some patience would be nice.

Right. My ask would be to move them all into the bug tracker instead of posting
them publicly. There I can filter for stuff that I know is already either being
discussed, already fixed in a tree, already delegated differently, or already
sitting in my backlog.

I would really appreciate if that would be possible.

> 
> Btw now you can delegate access to bugs to people outside of MAINTAINERS.

Oh, that's awesome! I was trying to delegate the last 2 weeks but was always
busy with other things (guess what :) ) ... and wondered how to send people
these reports.


I'll try playing with that next week.

> 
>> I'm sorry if I made you angry, but I hope you can see how I suspect (b) and why
>> it would make me angry.
> 
> No problems. I understand the problem with the maintainers load right
> now.
Thanks!

-- 
Cheers,

David