On 04.01.23 11:14, Christian Brauner wrote: > On Wed, Jan 04, 2023 at 11:04:06AM +0100, Linux kernel regression tracking (#info) wrote: >> [TLDR: This mail in primarily relevant for Linux kernel regression >> tracking. See link in footer if these mails annoy you.] >> >> On 04.01.23 01:57, hooanon05g@xxxxxxxxx wrote: >>> Christian Brauner: >>>> On Wed, Dec 28, 2022 at 12:27:55AM +0900, J. R. Okajima wrote: >>> ::: >>>>> I've found a behaviour got changed from v6.1 to v6.2-rc1 on ext3 (ext4). >>>> >>>> Hey, I'll try to take a look before new years. >>> >>> Now it becomes clear that the problem was on my side. >>> The "acl updates for v6.2" in mainline has nothing to deal with it. >>> Sorry for the noise. >> >> In that case: >> >> #regzbot resolve: turns out it was a local problem and not regression in >> the kernel > > When and how did regzbot start tracking this? None of the mails that > reported this issue to me contained any reference to regzbot. > > If something is currently classified as a regression it'd be good to let > the responsible maintainers and developers know that. That happens these days (again) -- since five, too be more precise, as I recently (again) changed how to handle that mails (some maintainers hated getting mails about adding reports to the tracking, but I recently decided they have to deal with that locally). But the mail that added this thread to the tracking was before that, sorry. :-/ https://lore.kernel.org/all/2aa5cc7e-ca00-22a7-5e2f-7eb73556181e@xxxxxxxxxxxxx/ Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did something stupid, please tell me, as explained on that page.
