From: Andreas Gruenbacher <agruenba@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Bob Peterson <rpeterso@redhat.com>, gfs2@lists.linux.dev
Subject: Re: [PATCH] gfs2: Initialize metapaths outside of __gfs2_iomap_get
Date: Wed, 1 Nov 2023 17:39:48 +0100 [thread overview]
Message-ID: <CAHc6FU6xYPCGK1MLpJ6JNsz6=Hej-ja7dgHUQLoVnis_vSKbAg@mail.gmail.com> (raw)
In-Reply-To: <7d405b46-7a22-414b-9ee6-99602ba309ea@roeck-us.net>
Guenter,
On Tue, Oct 31, 2023 at 1:59 AM Guenter Roeck <linux@roeck-us.net> wrote:
> Unfortunately that does not help. With the above on top of next-20231030, I still get:
>
> [ 15.531621] ------------[ cut here ]------------
> [ 15.531981] kernel BUG at fs/gfs2/bmap.c:695!
Sorry for this. I've pushed a fixed version to for-next already, so
things should be fine again now.
Thanks again,
Andres
next prev parent reply other threads:[~2023-11-01 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 18:33 [PATCH] gfs2: Initialize metapaths outside of __gfs2_iomap_get Guenter Roeck
2023-10-30 23:12 ` Andreas Gruenbacher
2023-10-31 0:58 ` Guenter Roeck
2023-11-01 16:39 ` Andreas Gruenbacher [this message]
2023-11-01 18:09 ` Guenter Roeck
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='CAHc6FU6xYPCGK1MLpJ6JNsz6=Hej-ja7dgHUQLoVnis_vSKbAg@mail.gmail.com' \
--to=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux@roeck-us.net \
--cc=rpeterso@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).