All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+cfc7cab3bb6eaa7c4de2@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] memory leak in ocfs2_new_path_from_path
Date: Thu, 04 Dec 2025 09:13:02 -0800	[thread overview]
Message-ID: <6931c11e.a70a0220.d98e3.01d8.GAE@google.com> (raw)
In-Reply-To: <ac84502c5bd65ae55b7bf92661760bef451097fc.camel@yandex.ru>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+cfc7cab3bb6eaa7c4de2@syzkaller.appspotmail.com
Tested-by: syzbot+cfc7cab3bb6eaa7c4de2@syzkaller.appspotmail.com

Tested on:

commit:         559e608c Merge tag 'ntfs3_for_6.19' of https://github...
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=15bdc01a580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3bdbe6509b080086
dashboard link: https://syzkaller.appspot.com/bug?extid=cfc7cab3bb6eaa7c4de2
compiler:       gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=14f2301a580000

Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2025-12-04 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ac84502c5bd65ae55b7bf92661760bef451097fc.camel@yandex.ru>
2025-12-04 17:13 ` syzbot [this message]
2025-11-07 17:11 [syzbot] [ocfs2?] memory leak in ocfs2_new_path_from_path syzbot
2025-12-02 19:51 ` syzbot

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=6931c11e.a70a0220.d98e3.01d8.GAE@google.com \
    --to=syzbot+cfc7cab3bb6eaa7c4de2@syzkaller.appspotmail.com \
    --cc=dmantipov@yandex.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.