public inbox for gfs2@lists.linux.dev
 help / color / mirror / Atom feed
From: Andrew Price <anprice@redhat.com>
To: Kun Hu <huk23@m.fudan.edu.cn>, Andreas Gruenbacher <agruenba@redhat.com>
Cc: "jjtan24@m.fudan.edu.cn" <jjtan24@m.fudan.edu.cn>,
	viro@zeniv.linux.org.uk, brauner@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	gfs2@lists.linux.dev
Subject: Re: Bug: slab-out-of-bounds Write in __bh_read
Date: Thu, 16 Jan 2025 14:30:38 +0000	[thread overview]
Message-ID: <eb78dcaf-5acc-4317-911d-cff3b53e424d@redhat.com> (raw)
In-Reply-To: <A184824F-B892-46D3-B086-556E9ACF4EA0@m.fudan.edu.cn>

On 16/01/2025 10:41, Kun Hu wrote:
> 
>> 2025年1月15日 02:05,Andreas Gruenbacher <agruenba@redhat.com> 写道:
>> I've posted a fix and pushed it to for-next:
>>
>> https://lore.kernel.org/gfs2/20250114175949.1196275-1-agruenba@redhat.com/
>>
>> Thanks for reporting!
>>
>> Andreas
> 
>> Syzlang reproducer: https://drive.google.com/file/d/1R9QDUP2r7MI4kYMiT_yn-tzm6NqmcEW-/view?usp=sharing
> 
> Hi Andreas,
> 
> Thank you for the patch. I tested it using the syscall reproducer and was still able to reproduce the issue.
> 
> Crash log: Link: https://github.com/pghk13/Kernel-Bug/blob/main/0103_6.13rc5_%E6%9C%AA%E6%8A%A5%E5%91%8A/%E5%AE%8C%E5%85%A8%E6%97%A0%E8%AE%B0%E5%BD%95/32-KASAN_%20slab-out-of-bounds%20Write%20in%20__bh_read/crashlog_0116_rc7%2Bpatch.txt
> 

That's not the slab-out-of-bounds failure. It's failing to mount with:

"kobject: kobject_add_internal failed for syz:syz with -EEXIST, don't 
try to register things with the same name in the same directory."

This can happen when a gfs2 fs is mounted with the same locktable twice, 
so I expect it's a problem in the test. Please make sure you're running 
the same reproducer from the original report, in the same way. The patch 
fixes both reproducers for me.

Andy


  reply	other threads:[~2025-01-16 14:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F0E0E5DD-572E-4F05-8016-46D36682C8BB@m.fudan.edu.cn>
     [not found] ` <brheoinx2gsmonf6uxobqicuxnqpxnsum26c3hcuroztmccl3m@lnmielvfe4v7>
     [not found]   ` <5757218E-52F8-49C7-95F1-9051EB51A2F3@m.fudan.edu.cn>
     [not found]     ` <6yd5s7fxnr7wtmluqa667lok54sphgtg4eppubntulelwidvca@ffyohkeovnyn>
     [not found]       ` <31A10938-C36E-40A2-8A1D-180BD95528DD@m.fudan.edu.cn>
2025-01-10 10:08         ` Bug: slab-out-of-bounds Write in __bh_read Jan Kara
2025-01-10 17:17           ` Kun Hu
2025-01-13 15:41             ` Andreas Gruenbacher
2025-01-13 15:54               ` Kun Hu
2025-01-13 16:12                 ` Andrew Price
2025-01-14 18:05                   ` Andreas Gruenbacher
     [not found]                     ` <958E28E8-3046-4030-963A-7A0789E8809C@m.fudan.edu.cn>
2025-01-15 13:37                       ` Andreas Gruenbacher
2025-01-16 10:41                     ` Kun Hu
2025-01-16 14:30                       ` Andrew Price [this message]
2025-01-13 16:24               ` Andreas Gruenbacher

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=eb78dcaf-5acc-4317-911d-cff3b53e424d@redhat.com \
    --to=anprice@redhat.com \
    --cc=agruenba@redhat.com \
    --cc=brauner@kernel.org \
    --cc=gfs2@lists.linux.dev \
    --cc=huk23@m.fudan.edu.cn \
    --cc=jjtan24@m.fudan.edu.cn \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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