gfs2 filesystem and dlm development
 help / color / mirror / Atom feed
From: Adrian Garcia Casado <adriangarciacasado42@gmail.com>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: gfs2@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gfs2: add missing __rcu annotation to i_gl in incore.h
Date: Fri, 24 Jul 2026 18:08:00 +0200	[thread overview]
Message-ID: <6a6396fb.1ec2db65.334318.e4b9@mx.google.com> (raw)

Hi Andreas,

Thanks for applying the patch!

For the record, I have successfully boot-tested the patched v7.2-rc4+
kernel on bare-metal x86_64 (Debian 13 native on an ASUS Vivobook).

To stress-test the kernel stability under load, I ran some heavy workloads:
- A standalone loopback mount of GFS2 (using lock_nolock) with I/O stress
  tests (100+ concurrent files).
- A full multi-threaded compilation of the PCSX2 emulator (using CMake
  and Ninja) with all CPU cores sustained at 100% load.

The system behaved completely stable with no deadlocks, hangs, or OOM.

Tested-by: Adrian Garcia Casado <adriangarciacasado42@gmail.com>

Best regards,
Adrian


             reply	other threads:[~2026-07-24 16:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 16:08 Adrian Garcia Casado [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-07-24 16:50 [PATCH] gfs2: add missing __rcu annotation to i_gl in incore.h Adrian Garcia Casado
2026-07-24 16:08 Adrian Garcia Casado
2026-07-23 17:44 Adrian Garcia Casado
2026-06-30 10:02 Adrian Garcia Casado
2026-07-24 15:32 ` Andreas Gruenbacher
     [not found]   ` <CA+cq9YO=6PJ1Xx97vMuWsv+h8ebe2a8mKYoktuyZOY6MBKRxzg@mail.gmail.com>
2026-07-24 16:17     ` Andreas Gruenbacher
2026-06-30  9:55 Adrian Garcia Casado
2026-06-18 13:56 Adrian
2026-06-18 13:56 Adrian

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=6a6396fb.1ec2db65.334318.e4b9@mx.google.com \
    --to=adriangarciacasado42@gmail.com \
    --cc=agruenba@redhat.com \
    --cc=gfs2@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.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