linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+5b6ed16da1077f45bc8e@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] possible fix
Date: Tue, 16 Jul 2024 23:36:35 -0700	[thread overview]
Message-ID: <00000000000001a5f1061d6bafaf@google.com> (raw)
In-Reply-To: <000000000000be9914061763f17a@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: possible fix
Author: almaz.alexandrovich@paragon-software.com

#syz test: https://github.com/Paragon-Software-Group/linux-ntfs3.git 
562d060bed6637fbc3bc22802a0a0c5b00e12a38






  parent reply	other threads:[~2024-07-17  6:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01 12:51 [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in attr_make_nonresident syzbot
2024-07-15  9:41 ` [syzbot] " syzbot
2024-07-17  6:36 ` syzbot [this message]
2024-07-17  8:20 ` [syzbot] before possible fix syzbot
2024-08-23 16:04 ` [syzbot] BUG: unable to handle kernel NULL pointer dereference in attr_make_nonresident syzbot
2024-08-27 16:17 ` [syzbot] [ntfs3?] " syzbot
2024-09-03 11:24   ` Konstantin Komarov
  -- strict thread matches above, loose matches on Subject: below --
2022-11-30 12:51 [syzbot] possible deadlock in ntfs_fiemap syzbot
2024-07-20  7:43 ` [syzbot] possible fix syzbot
2022-10-18  5:47 [syzbot] possible deadlock in ni_fiemap syzbot
2024-07-20  7:43 ` [syzbot] possible fix syzbot
2022-10-17  7:43 [syzbot] possible deadlock in attr_data_get_block syzbot
2024-07-17  6:24 ` [syzbot] possible fix 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=00000000000001a5f1061d6bafaf@google.com \
    --to=syzbot+5b6ed16da1077f45bc8e@syzkaller.appspotmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).