public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+list7a6f269bbee45c565136@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netfs@lists.linux.dev,
	 syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly netfs report (Nov 2024)
Date: Thu, 21 Nov 2024 01:50:23 -0800	[thread overview]
Message-ID: <673f025f.050a0220.363a1b.00fa.GAE@google.com> (raw)

Hello netfs maintainers/developers,

This is a 31-day syzbot report for the netfs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/netfs

During the period, 3 new issues were detected and 0 were fixed.
In total, 9 issues are still open and 1 has already been fixed.

Some of the still happening issues:

Ref Crashes Repro Title
<1> 58      Yes   KASAN: slab-use-after-free Read in iov_iter_revert
                  https://syzkaller.appspot.com/bug?extid=2625ce08c2659fb9961a
<2> 4       Yes   kernel BUG in iov_iter_revert (2)
                  https://syzkaller.appspot.com/bug?extid=404b4b745080b6210c6c
<3> 1       No    WARNING in netfs_writepages
                  https://syzkaller.appspot.com/bug?extid=06023121b0153752a3d3

---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders

To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem

You may send multiple commands in a single email message.

                 reply	other threads:[~2024-11-21  9:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=673f025f.050a0220.363a1b.00fa.GAE@google.com \
    --to=syzbot+list7a6f269bbee45c565136@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfs@lists.linux.dev \
    --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