From: Venkat <venkat88@linux.ibm.com>
To: tytso@mit.edu, robh@kernel.org,
angelogioacchino.delregno@collabora.com,
chunfeng.yun@mediatek.com, vkoul@kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: fstests@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>
Subject: Re: [next-20250212] FStests generic/451 on EXT4 FS resulting in kernel OOPs
Date: Sun, 16 Feb 2025 23:32:24 +0530 [thread overview]
Message-ID: <7F085D3B-4AE5-4DDC-94BB-59EF8A67A592@linux.ibm.com> (raw)
I did attempt git bisect, and the first bad commit is d49e636ed7014be354d1ee279b8f4957e8def389.
Git bisect log:
#git bisect log
#git bisect start
# status: waiting for both good and bad commits
# good: [a64dcfb451e254085a7daee5fe51bf22959d52d3] Linux 6.14-rc2
git bisect good a64dcfb451e254085a7daee5fe51bf22959d52d3
# status: waiting for bad commit, 1 good commit known
# bad: [c674aa7c289e51659e40dda0f954886ef7f80042] Add linux-next specific files for 20250212
git bisect bad c674aa7c289e51659e40dda0f954886ef7f80042
# good: [0a354ebcff3e3564281f2ee70b7094f5d16b762e] Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git
git bisect good 0a354ebcff3e3564281f2ee70b7094f5d16b762e
# good: [21abbfe377b86bac23e3d167f002a492391555c7] Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
git bisect good 21abbfe377b86bac23e3d167f002a492391555c7
# good: [fcd8e79b9c555ea05cca4ab4593e3fa02722158f] Merge branch 'usb-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
git bisect good fcd8e79b9c555ea05cca4ab4593e3fa02722158f
# bad: [8b5e9ed3e14f98a0dfa9a2e15654c0f4d94ac64c] Merge branch 'pwm/for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git
git bisect bad 8b5e9ed3e14f98a0dfa9a2e15654c0f4d94ac64c
# bad: [4e91a64bcf478f6f7cf7aab043d80ca671367348] Merge branch 'staging-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
git bisect bad 4e91a64bcf478f6f7cf7aab043d80ca671367348
# good: [7b465a0d58c19a45ddf81c90bc8ba04693de038b] iio: light: adux1020: Drop unneeded assignment for cache_type
git bisect good 7b465a0d58c19a45ddf81c90bc8ba04693de038b
# good: [66b800119cc5ced59aa45d523e8ef9af54211abd] Merge branch 'togreg' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
git bisect good 66b800119cc5ced59aa45d523e8ef9af54211abd
# bad: [1fad5171135d31d3d9258715c7d3fefa378797e0] Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-w1.git
git bisect bad 1fad5171135d31d3d9258715c7d3fefa378797e0
# good: [0d8db251dd15d2e284f5a6a53bc2b869f3eca711] phy: qcom: qmp-pcie: Add X1P42100 Gen4x4 PHY
git bisect good 0d8db251dd15d2e284f5a6a53bc2b869f3eca711
# bad: [d49e636ed7014be354d1ee279b8f4957e8def389] Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git
git bisect bad d49e636ed7014be354d1ee279b8f4957e8def389
# good: [88c0053baed659acd85b87dd52cbd75f3d8806be] phy: Use (of|device)_property_present() for non-boolean properties
git bisect good 88c0053baed659acd85b87dd52cbd75f3d8806be
# first bad commit: [d49e636ed7014be354d1ee279b8f4957e8def389] Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git
#
Regards,
Venkat.
next reply other threads:[~2025-02-16 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 18:02 Venkat [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-13 5:51 [next-20250212] FStests generic/451 on EXT4 FS resulting in kernel OOPs Venkat Rao Bagalkote
2025-02-13 6:08 ` Sourabh Jain
2025-02-13 18:52 ` Theodore Ts'o
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=7F085D3B-4AE5-4DDC-94BB-59EF8A67A592@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunfeng.yun@mediatek.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
--cc=venkat88@linux.vnet.ibm.com \
--cc=vkoul@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