mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+0e70362e1726b5a7502e@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, fred@cloudflare.com,
	 linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
	 syzkaller-bugs@googlegroups.com, zohar@linux.ibm.com
Subject: Re: [syzbot] [ntfs3?] WARNING in truncate_setsize
Date: Fri, 02 Oct 2026 10:15:02 -0700	[thread overview]
Message-ID: <6abfe696.7503fbd6.2d3f6.0024.GAE@google.com> (raw)
In-Reply-To: <6abc1c9e.00649fcc.35d151.00e6.GAE@google.com>

syzbot has bisected this issue to:

commit b80bed5c871a80151351342c065579405ce77145
Author: Mimi Zohar <zohar@linux.ibm.com>
Date:   Tue Jul 28 00:39:41 2026 +0000

    ima: Instantiate file_truncate and path_truncate hooks

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1302e035580000
start commit:   ce1e0223d8ad Merge tag 'devicetree-fixes-for-7.3-2' of git..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=1082e035580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1702e035580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=718e346eb0b8f38
dashboard link: https://syzkaller.appspot.com/bug?extid=0e70362e1726b5a7502e
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=143da725580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=113236c9580000

Reported-by: syzbot+0e70362e1726b5a7502e@syzkaller.appspotmail.com
Fixes: b80bed5c871a ("ima: Instantiate file_truncate and path_truncate hooks")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2026-10-02 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 20:16 syzbot
2026-10-02  8:34 ` syzbot
2026-10-02 17:15 ` syzbot [this message]

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=6abfe696.7503fbd6.2d3f6.0024.GAE@google.com \
    --to=syzbot+0e70362e1726b5a7502e@syzkaller.appspotmail.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=fred@cloudflare.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=zohar@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
all inboxes | Powered by JetHome®