mirror of https://lore.kernel.org/lkml/
 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,
	syzbot <syzbot+e3973c409251e136fdd0@syzkaller.appspotmail.com>,
	syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org,
	sjb7183@psu.edu
Subject: [PATCH 0/3] nilfs2: fix log writer related issues
Date: Mon, 20 May 2024 22:26:18 +0900	[thread overview]
Message-ID: <20240520132621.4054-1-konishi.ryusuke@gmail.com> (raw)
In-Reply-To: <0000000000001a167a05ebc4f62b@google.com>

Hello Andrew,

Please apply this series as bug fixes.

This bug fix series covers three nilfs2 log writer-related issues,
including a timer use-after-free issue and potential deadlock issue on
unmount, and a potential freeze issue in event synchronization found
during their analysis.  Details are described in each commit log.

thank you always.

Ryusuke Konishi

Ryusuke Konishi (3):
  nilfs2: fix use-after-free of timer for log writer thread
  nilfs2: fix unexpected freezing of nilfs_segctor_sync()
  nilfs2: fix potential hang in nilfs_detach_log_writer()

 fs/nilfs2/segment.c | 63 +++++++++++++++++++++++++++++++++++----------
 1 file changed, 50 insertions(+), 13 deletions(-)

-- 
2.34.1


  reply	other threads:[~2024-05-20 13:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 10:07 [syzbot] INFO: task hung in nilfs_detach_log_writer syzbot
2024-05-20 13:26 ` Ryusuke Konishi [this message]
2024-05-20 13:26   ` [PATCH 1/3] nilfs2: fix use-after-free of timer for log writer thread Ryusuke Konishi
2024-05-20 13:26   ` [PATCH 2/3] nilfs2: fix unexpected freezing of nilfs_segctor_sync() Ryusuke Konishi
2024-05-20 13:26   ` [PATCH 3/3] nilfs2: fix potential hang in nilfs_detach_log_writer() 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=20240520132621.4054-1-konishi.ryusuke@gmail.com \
    --to=konishi.ryusuke@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=sjb7183@psu.edu \
    --cc=syzbot+e3973c409251e136fdd0@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
all inboxes | Powered by JetHome®