Re: [v6.1] kernel BUG in ext4_writepages

[Linux regression tracking (Thorsten Leemhuis)]

On 15.08.23 18:31, Muhammad Usama Anjum wrote:
> Thank you for looking at the email.
> 
> On 8/15/23 3:05 AM, Theodore Ts'o wrote:
>> On Mon, Aug 14, 2023 at 10:35:57AM +0500, Muhammad Usama Anjum wrote:
>>>> The last refactoring was done by 4e7ea81db53465 on this code in 2013. The
>>>> code segment in question is present from even before that. It means that
>>>> this bug is present for several years. 4.14 is the most old kernel being
>>>> maintained today. So it affects all current LTS and mainline kernels. I'll
>>>> report 4e7ea81db53465 with regzbot for proper tracking. Thus probably the
>>>> bug report will get associated with all LTS kernels as well.
>>>>
>>>> #regzbot title: Race condition between buffer write and page_mkwrite
>>>
>>> #regzbot title: ext4: Race condition between buffer write and page_mkwrite
>>
>> If it's a long-standing bug, then it's really not something I consider
>> a regression.  That being said, you're assuming that the refactoring
>> is what has introduced the bug; that's not necessarily case.
> The bug was introduced by the following patch:
> 9c3569b50f12 ("ext4: add delalloc support for inline data")

Which was v3.8-rc1 afaics.

> https://lore.kernel.org/all/1351047338-4963-7-git-send-email-tm@xxxxxx/
> The bug is in the inline data feature addition patches itself.
> 
> Should I remove this regression from regzbot marking it as not regression
> and only a long-standing bug?

Let me do that:

#regzbot inconclusive: regression from the 3.8 days, tracking doesn't
really gain us anything

To explain: not sure how Linus sees it, but if the culprit was merged
that long ago there is not much worth in tracking it, as there is no
easy way to fix it with a revert or something anyway. Sure, the issue
nevertheless should not remain unfixed, but lets trust Ted here that
he'll sooner or later take care of it when he sees fit.

Ciao, Thorsten