From: Sachin Sant <sachinp@linux.ibm.com>
To: Dave Chinner <david@fromorbit.com>
Cc: dchinner@redhat.com, linux-xfs@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-next@vger.kernel.org,
riteshh@linux.ibm.com
Subject: Re: BUG xfs_buf while running tests/xfs/435 (next-20220715)
Date: Mon, 18 Jul 2022 18:10:30 +0530 [thread overview]
Message-ID: <E1661B4B-D2BF-465F-8C65-935909A2E527@linux.ibm.com> (raw)
In-Reply-To: <20220718080112.GS3861211@dread.disaster.area>
> Fix it by removing the xfs_buf_init/terminate wrappers that just
> allocate and destroy the xfs_buf slab, and move them to the same
> place that all the other slab caches are set up and destroyed.
>
> Reported-by: Sachin Sant <sachinp@linux.ibm.com>
> Fixes: 298f34224506 ("xfs: lockless buffer lookup")
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
Thanks. The patch fixes the reported problem for me.
Tested-by: Sachin Sant <sachinp@linux.ibm.com>
- Sachin
prev parent reply other threads:[~2022-07-18 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 6:31 BUG xfs_buf while running tests/xfs/435 (next-20220715) Sachin Sant
2022-07-18 8:01 ` Dave Chinner
2022-07-18 12:40 ` Sachin Sant [this message]
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=E1661B4B-D2BF-465F-8C65-935909A2E527@linux.ibm.com \
--to=sachinp@linux.ibm.com \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=riteshh@linux.ibm.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