From: "Theodore Ts'o" <tytso@mit.edu>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lkft-triage@lists.linaro.org,
linux-ext4 <linux-ext4@vger.kernel.org>,
LTP List <ltp@lists.linux.it>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>
Subject: Re: next: kernel BUG at fs/ext4/mballoc.c:4369!
Date: Mon, 17 Jul 2023 00:31:11 -0400 [thread overview]
Message-ID: <20230717043111.GA3842864@mit.edu> (raw)
In-Reply-To: <CA+G9fYv2FRpLqBZf34ZinR8bU2_ZRAUOjKAD3+tKRFaEQHtt8Q@mail.gmail.com>
On Sun, Jul 16, 2023 at 11:32:51AM +0530, Naresh Kamboju wrote:
> Following kernel BUG noticed while testing LTP fs testing on x86_64
> arch x86_64 on the Linux next-20230716 built with clang toolchain.
Hmm, I'm not seeing the next-20230716 tag at:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/
or
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next-history.git/
I see a tag for next-20230717 and for next-20230714, but not
next-20230716. Was this a typo? Does it reproduce on the
next-20230717 tree?
Also, since I don't use LTP, can you give me a trimmed-down
reproducer, to save me some time?
Thanks!!
- Ted
next prev parent reply other threads:[~2023-07-17 4:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 6:02 next: kernel BUG at fs/ext4/mballoc.c:4369! Naresh Kamboju
2023-07-17 4:31 ` Theodore Ts'o [this message]
2023-07-17 5:06 ` Naresh Kamboju
2023-07-17 5:43 ` Ritesh Harjani
2023-07-17 7:12 ` Ojaswin Mujoo
2023-07-17 14:34 ` Ritesh Harjani
2023-07-17 21:34 ` Theodore Ts'o
2023-07-18 1:57 ` Ritesh Harjani
2023-07-18 9:10 ` [LTP] " Petr Vorel
2023-07-18 11:47 ` Naresh Kamboju
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=20230717043111.GA3842864@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=naresh.kamboju@linaro.org \
--cc=ojaswin@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;
as well as URLs for NNTP newsgroup(s).