[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230717043111.GA3842864@mit.edu>
Date: Mon, 17 Jul 2023 00:31:11 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: open list <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>, lkft-triage@...ts.linaro.org,
linux-ext4 <linux-ext4@...r.kernel.org>,
LTP List <ltp@...ts.linux.it>,
Andrew Morton <akpm@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>,
Dan Carpenter <dan.carpenter@...aro.org>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Ojaswin Mujoo <ojaswin@...ux.ibm.com>
Subject: Re: next: kernel BUG at fs/ext4/mballoc.c:4369!
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
Powered by blists - more mailing lists