From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6FA3922154E; Wed, 26 Feb 2025 14:36:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740580604; cv=none; b=HFY9GJJty23zIHnShwGsrHiess+nzwH9VUj9VGEjMf/LOq2qdAEt7P16PP3cfwAYMYtPKrkSWtlr3g/AHivBlY9Yzhylvg3vmF7GALXl+pbBOdtrTL7AlSb002qhnZAUpERdkKZZejHPMDNQqSPRpXsgFi2yeXQ+ErLFVaPvLdE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740580604; c=relaxed/simple; bh=e/RvFSeK3mvDDNrCtjDF+JKRspPdp9Qhr7cGfqkAXgk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=WQF3ppIXlcafydjX8BkJzzgEmCVCK2Ktfxq6AgfzJUJD1t8JHH9QotaEM1s5ptELcOefe0POdD9yoWZR+yEFlZOPGWiZq39TDGs0vQJ4/cYdWzb4E5wKOWNRnMjLJFg8n/xXya5/raoDrdMqdY0a53+OtrE6EIGAH0RH0F8gu4M= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=lstsQ5sM; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="lstsQ5sM" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D2200C4CED6; Wed, 26 Feb 2025 14:36:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1740580603; bh=e/RvFSeK3mvDDNrCtjDF+JKRspPdp9Qhr7cGfqkAXgk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=lstsQ5sMAv5GyXkm1iIjjXxNC9d6KKe3dqnWBZ5+3kKGHsYHgeFsQxuaU2MbjaD18 yqilNJPVKU4V87oJ9pZuO9FlCuapIdXogUGuvE20lY9ONfDbUjBczIXfui0YbS4z5c RV9HikhXvszKKyGF8njsfUnXc9fUyEGoMzW+MsiM= Date: Wed, 26 Feb 2025 15:35:34 +0100 From: Greg KH To: Chuck Lever Cc: Takashi Iwai , regressions@lists.linux.dev, linux-fsdevel@vger.kernel.org, stable@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [REGRESSION] Chrome and VSCode breakage with the commit b9b588f22a0c Message-ID: <2025022626-octane-rickety-304a@gregkh> References: <874j0lvy89.wl-tiwai@suse.de> <87jz9d5cdp.wl-tiwai@suse.de> <263acb8f-2864-4165-90f7-6166e68180be@oracle.com> <87h64g4wr1.wl-tiwai@suse.de> <7a4072d6-3e66-4896-8f66-5871e817d285@oracle.com> <2025022657-credit-undrilled-81f1@gregkh> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2025022657-credit-undrilled-81f1@gregkh> On Wed, Feb 26, 2025 at 03:26:44PM +0100, Greg KH wrote: > On Wed, Feb 26, 2025 at 09:20:20AM -0500, Chuck Lever wrote: > > On 2/26/25 9:16 AM, Takashi Iwai wrote: > > > On Wed, 26 Feb 2025 15:11:04 +0100, > > > Chuck Lever wrote: > > >> > > >> On 2/26/25 3:38 AM, Takashi Iwai wrote: > > >>> On Sun, 23 Feb 2025 16:18:41 +0100, > > >>> Chuck Lever wrote: > > >>>> > > >>>> On 2/23/25 3:53 AM, Takashi Iwai wrote: > > >>>>> [ resent due to a wrong address for regression reporting, sorry! ] > > >>>>> > > >>>>> Hi, > > >>>>> > > >>>>> we received a bug report showing the regression on 6.13.1 kernel > > >>>>> against 6.13.0. The symptom is that Chrome and VSCode stopped working > > >>>>> with Gnome Scaling, as reported on openSUSE Tumbleweed bug tracker > > >>>>> https://bugzilla.suse.com/show_bug.cgi?id=1236943 > > >>>>> > > >>>>> Quoting from there: > > >>>>> """ > > >>>>> I use the latest TW on Gnome with a 4K display and 150% > > >>>>> scaling. Everything has been working fine, but recently both Chrome > > >>>>> and VSCode (installed from official non-openSUSE channels) stopped > > >>>>> working with Scaling. > > >>>>> .... > > >>>>> I am using VSCode with: > > >>>>> `--enable-features=UseOzonePlatform --enable-features=WaylandWindowDecorations --ozone-platform-hint=auto` and for Chrome, I select `Preferred Ozone platform` == `Wayland`. > > >>>>> """ > > >>>>> > > >>>>> Surprisingly, the bisection pointed to the backport of the commit > > >>>>> b9b588f22a0c049a14885399e27625635ae6ef91 ("libfs: Use d_children list > > >>>>> to iterate simple_offset directories"). > > >>>>> > > >>>>> Indeed, the revert of this patch on the latest 6.13.4 was confirmed to > > >>>>> fix the issue. Also, the reporter verified that the latest 6.14-rc > > >>>>> release is still affected, too. > > >>>>> > > >>>>> For now I have no concrete idea how the patch could break the behavior > > >>>>> of a graphical application like the above. Let us know if you need > > >>>>> something for debugging. (Or at easiest, join to the bugzilla entry > > >>>>> and ask there; or open another bug report at whatever you like.) > > >>>>> > > >>>>> BTW, I'll be traveling tomorrow, so my reply will be delayed. > > >>>>> > > >>>>> > > >>>>> thanks, > > >>>>> > > >>>>> Takashi > > >>>>> > > >>>>> #regzbot introduced: b9b588f22a0c049a14885399e27625635ae6ef91 > > >>>>> #regzbot monitor: https://bugzilla.suse.com/show_bug.cgi?id=1236943 > > >>>> > > >>>> We received a similar report a few days ago, and are likewise puzzled at > > >>>> the commit result. Please report this issue to the Chrome development > > >>>> team and have them come up with a simple reproducer that I can try in my > > >>>> own lab. I'm sure they can quickly get to the bottom of the application > > >>>> stack to identify the misbehaving interaction between OS and app. > > >>> > > >>> Do you know where to report to? > > >> > > >> You'll need to drive this, since you currently have a working > > >> reproducer. > > > > > > No, I don't have, I'm merely a messenger. > > > > Whoever was the original reporter has the ability to reproduce this and > > answer any questions the Chrome team might have. Please have them drive > > this. I'm already two steps removed, so it doesn't make sense for me to > > report a problem for which I have no standing. > > Ugh, no. The bug was explictly bisected to the offending commit. We > should just revert that commit for now and it can come back in the > future if the root-cause is found. > > As the revert seems to be simple, and builds here for me, I guess I'll > have to send it in. {sigh} > > Takashi, thanks for the report and the bisection, much appreciated. Now sent: https://lore.kernel.org/r/2025022644-blinked-broadness-c810@gregkh