From: Matthew Wilcox <willy@infradead.org>
To: Haichi Wang <wanghaichi@tju.edu.cn>
Cc: dave.hansen@linux.intel.com, brauner@kernel.org, hpa@zytor.com,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
tglx@linutronix.de, bp@alien8.de, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, luto@kernel.org, x86@kernel.org,
mingo@redhat.com, kent.overstreet@linux.dev, jack@suse.cz,
syzkaller@googlegroups.com
Subject: Re: Kernel bug: "general protection fault in bch2_btree_path_traverse_one"
Date: Fri, 20 Dec 2024 13:53:25 +0000 [thread overview]
Message-ID: <Z2V21UH_3FuNDoa1@casper.infradead.org> (raw)
In-Reply-To: <AOAA*AACIqMsH7SiGMkHgaoE.1.1734695024950.Hmail.3014218099@tju.edu.cn>
On Fri, Dec 20, 2024 at 07:43:44PM +0800, Haichi Wang wrote:
> Dear Linux maintainers and reviewers:
> We are reporting a Linux kernel bug titled **general protection fault in bch2_btree_path_traverse_one**, discovered using a modified version of Syzkaller.
No, you aren't. This is a terrible bug report, and you seem to have
sent several with the same defects. First, read:
https://blog.regehr.org/archives/2037
Then, specifically to reporting a kernel bug *LOOK AT HOW OTHER PEOPLE
DO IT*. Your email includes lots of stuff that is of no help and
doesn't include the most important thing -- the kernel logs from around
the time of the failure.
> ### Affected Files
> The affected files, as obtained from the VM log, are listed below. The corresponding maintainers were identified using `./scripts/get_maintainer.pl`:
> fs/bcachefs/btree_update_interior.c
> fs/bcachefs/alloc_foreground.c
> fs/bcachefs/btree_iter.c
> fs/bcachefs/btree_trans_commit.c
> fs/namespace.c
> arch/x86/entry/common.c
> fs/bcachefs/recovery.c
> fs/bcachefs/recovery_passes.c
> fs/bcachefs/super.c
> fs/bcachefs/fs.c
> fs/super.c
This is useless.
> ### Kernel Versions
> - **Kernel Version Tested:** v6.12-rc6:59b723cd2adbac2a34fc8e12c74ae26ae45bf230
> - **Latest Kernel Version Reproduced On:** f44d154d6e3d633d4c49a5d6a8aed0e4684ae25e
Useful
> ### Environment Details
> - **QEMU Version:** QEMU emulator version 4.2.1 (Debian 1:4.2-3ubuntu6.29)
> - **GCC Version:** gcc (Ubuntu 11.4.0-2ubuntu1~20.04) 11.4.0
> - **Syzkaller Version:** 2b3ef1577cde5da4fd1f7ece079731e140351177
Useful
> ### Attached Files
> We have attached the following files to assist in reproducing and diagnosing the bug:
> - **Bug Title:** `bugtitle`
> - **Bug Report:** `report`
> - **Machine Information:** `machineInfo`
> - **Kernel Config:** `config`
> - **Compiled Kernel Image:** `vmlinux`
You didn't attach these things, but please don't.
We want the stacktrace. Preferably passed through
scripts/decode_stacktrace.sh so we get nice symbols.
next prev parent reply other threads:[~2024-12-20 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 11:43 Kernel bug: "general protection fault in bch2_btree_path_traverse_one" Haichi Wang
2024-12-20 13:53 ` Matthew Wilcox [this message]
2024-12-20 15:01 ` Kent Overstreet
2025-01-07 15:01 ` Dmitry Vyukov
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=Z2V21UH_3FuNDoa1@casper.infradead.org \
--to=willy@infradead.org \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=syzkaller@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=wanghaichi@tju.edu.cn \
--cc=x86@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