Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzbot <syzbot+9982fb8d18eba905abe2@syzkaller.appspotmail.com>,
	syzkaller-bugs@googlegroups.com, bugreport@valiantsec.com
Subject: [PATCH 0/2] nilfs2: fix null-ptr-deref bugs on block tracepoints
Date: Thu,  7 Nov 2024 01:07:31 +0900	[thread overview]
Message-ID: <20241106160811.3316-1-konishi.ryusuke@gmail.com> (raw)
In-Reply-To: <672270b5.050a0220.3c8d68.052a.GAE@google.com>

Hi Andrew, please add this series to the queue for the next cycle.

This series fixes null pointer dereference bugs that occur when using
nilfs2 and two block-related tracepoints.

Thanks,
Ryusuke Konishi

Ryusuke Konishi (2):
  nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint
  nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint

 fs/nilfs2/btnode.c  | 2 --
 fs/nilfs2/gcinode.c | 4 +---
 fs/nilfs2/mdt.c     | 1 -
 fs/nilfs2/page.c    | 2 +-
 4 files changed, 2 insertions(+), 7 deletions(-)

-- 
2.43.0


  reply	other threads:[~2024-11-06 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30 17:45 [syzbot] [nilfs?] general protection fault in touch_buffer syzbot
2024-11-06 16:07 ` Ryusuke Konishi [this message]
2024-11-06 16:07   ` [PATCH 1/2] nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint Ryusuke Konishi
2024-11-06 16:07   ` [PATCH 2/2] nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint Ryusuke Konishi

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=20241106160811.3316-1-konishi.ryusuke@gmail.com \
    --to=konishi.ryusuke@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugreport@valiantsec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=syzbot+9982fb8d18eba905abe2@syzkaller.appspotmail.com \
    --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