Linux filesystem development
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd@bsbernd.com>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: "Vlastimil Babka" <vbabka@suse.cz>,
	"Miklos Szeredi" <miklos@szeredi.hu>,
	"Matthew Wilcox" <willy@infradead.org>,
	"Christian Heusel" <christian@heusel.eu>,
	"Josef Bacik" <josef@toxicpanda.com>,
	"Miklos Szeredi" <mszeredi@redhat.com>,
	regressions@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
	"Mantas Mikulėnas" <grawity@gmail.com>
Subject: Re: [REGRESSION][BISECTED] Crash with Bad page state for FUSE/Flatpak related applications since v6.13
Date: Sat, 8 Feb 2025 01:02:38 +0100	[thread overview]
Message-ID: <b828162e-716a-4ccd-95bb-d51e31cea538@bsbernd.com> (raw)
In-Reply-To: <CAJnrk1atv4N-BDWnwmESvczJhkayXyQqnLEypkmuJNKBa6gq8A@mail.gmail.com>



On 2/7/25 19:40, Joanne Koong wrote:
> On Fri, Feb 7, 2025 at 3:16 AM Bernd Schubert <bernd@bsbernd.com> wrote:
>>
>>
>>
>> On 2/7/25 11:55, Vlastimil Babka wrote:
>>> On 2/7/25 11:43, Miklos Szeredi wrote:
>>>> On Fri, 7 Feb 2025 at 11:25, Vlastimil Babka <vbabka@suse.cz> wrote:
>>>>
>>>>> Could be a use-after free of the page, which sets PG_lru again. The list
>>>>> corruptions in __rmqueue_pcplist also suggest some page manipulation after
>>>>> free. The -1 refcount suggests somebody was using the page while it was
>>>>> freed due to refcount dropping to 0 and then did a put_page()?
>>>>
>>>> Can you suggest any debug options that could help pinpoint the offender?
>>>
>>> CONFIG_DEBUG_VM enables a check in put_page_testzero() that would catch the
>>> underflow (modulo a tiny race window where it wouldn't). Worth trying.
>>
>> I typically run all of my tests with these options enabled
>>
>> https://github.com/bsbernd/tiny-qemu-virtio-kernel-config
>>
>>
>> If Christian or Mantas could tell me what I need to install and run, I
>> could probably quickly give it a try.
>>
> 
> Copying/pasting from [1], these are the repro steps that's listed:
> 
> 1) Install Bottles: flatpak install flathub com.usebottles.bottles
> 2) Open Bottles and create a bottle
> 3) In a terminal open the kernel log using dmesg/journalctl in follow mode
> 4) Once the bottle has been initialized, open it, select "Run
> Executable" and point it at any Windows executable
> Note that at that same moment a BUG: Bad page state in process fuse
> mainloop error message will appear and the system will become
> unresponsive (keyboard and mouse might still work but you'll be unable
> to actually do anything, open or close any application, or even reboot
> or shutdown; you are able to ping the device and initiate an SSH
> connection but all it does is just display the banner)
> 

Thanks Joanne! Hmm, I found "wmplayer" in a c drive, but there doesn't
happen much

   5241 pts/0    Ss     0:00 -bash
   5317 pts/1    S+     0:00 /home/bernd/.var/app/com.usebottles.bottles/data/bottles/runners/soda-9.0-1/bin/wi
   5319 ?        Ss     0:01 /home/bernd/.var/app/com.usebottles.bottles/data/bottles/runners/soda-9.0-1/bin/wi
   5321 pts/1    S+     0:01 C:\windows\system32\wineboot.exe --init
   5345 ?        Ssl    0:01 C:\windows\system32\services.exe
   5348 ?        Ssl    0:00 C:\windows\system32\winedevice.exe
   5359 ?        Ssl    0:01 C:\windows\system32\winedevice.exe
   5360 ?        I      0:00 [kworker/u130:0-rpciod]

It runs it, but no system issue. I had also tried "Obfuscate", but didn't
manage to feed it a file - it runs in the sandbox and no access to
my $HOME.

I need to see is if I can find some other files, but very late here
and busy with something else. It also runs in x2gokdrive and wine
then over another ssh hope to the vm guest, which has a kernel with all
these debug options - slow.

Bernd






  reply	other threads:[~2025-02-08  0:02 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 10:53 [REGRESSION][BISECTED] Crash with Bad page state for FUSE/Flatpak related applications since v6.13 Christian Heusel
2025-02-07  9:34 ` Miklos Szeredi
2025-02-07  9:45   ` Matthew Wilcox
2025-02-07 10:25     ` Vlastimil Babka
2025-02-07 10:43       ` Miklos Szeredi
2025-02-07 10:55         ` Vlastimil Babka
2025-02-07 11:16           ` Bernd Schubert
2025-02-07 18:21             ` Bernd Schubert
2025-02-07 18:40             ` Joanne Koong
2025-02-08  0:02               ` Bernd Schubert [this message]
2025-02-08 12:25                 ` Mantas Mikulėnas
2025-02-07 20:35             ` Mantas Mikulėnas
2025-02-07 11:00   ` Mantas Mikulėnas
2025-02-07 16:49   ` Vlastimil Babka
2025-02-07 17:29     ` Josef Bacik
2025-02-07 18:39       ` Vlastimil Babka
2025-02-07 22:29         ` Matthew Wilcox
2025-02-08  0:22         ` Joanne Koong
2025-02-08 10:11           ` Matthew Wilcox
2025-02-08 15:46             ` Joanne Koong
2025-02-10  8:27               ` Vlastimil Babka
2025-02-10 18:13                 ` Joanne Koong
2025-02-10 19:12                   ` Josef Bacik
2025-02-10 19:42                     ` Jeff Layton
2025-02-10 20:36                     ` Matthew Wilcox
2025-02-10 22:38                       ` Jeff Layton
2025-02-11 14:01                         ` Jeff Layton
2025-02-11 19:23                           ` Joanne Koong
2025-02-11 19:41                             ` Jeff Layton
2025-02-11 21:10                               ` Joanne Koong
2025-02-11 21:01                             ` Vlastimil Babka
2025-02-11 21:21                               ` Joanne Koong
2025-02-10 18:58                 ` Jeff Layton
2025-02-12 18:48               ` Joanne Koong
2025-02-10  8:52   ` [PATCH] fuse: prevent folio use-after-free in readahead Vlastimil Babka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b828162e-716a-4ccd-95bb-d51e31cea538@bsbernd.com \
    --to=bernd@bsbernd.com \
    --cc=christian@heusel.eu \
    --cc=grawity@gmail.com \
    --cc=joannelkoong@gmail.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@redhat.com \
    --cc=regressions@lists.linux.dev \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox