mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Cc: linux-nilfs <linux-nilfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	 syzbot+8baf9a79a3ffc6271cb6@syzkaller.appspotmail.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] nilfs2: fix BUG in nilfs_copy_dirty_pages() on dirty state mismatch
Date: Tue, 28 Jul 2026 16:28:29 -0700	[thread overview]
Message-ID: <61617a0287d6e0bf0914088712d0b57d2e5cec75.camel@dubeyko.com> (raw)
In-Reply-To: <CAKFNMonu620z87=b=+9Xwn44Zr9-CssQkn=mes5EqEc=iJUm0g@mail.gmail.com>

Hi Ryusuke,

On Tue, 2026-07-28 at 13:32 +0900, Ryusuke Konishi wrote:
> > 

> 
> Hi Viacheslav,
> 
> Sorry for the disturbance while you are busy.
> 
> Could you please pick up the following four pending patches -
> including this one - for the next cycle at your convenience?
> Excluding those already applied, these are the ones submitted by me
> or
> requested for direct pick-up since the weekend before last:
> 
> - [PATCH] nilfs2: fix slab-out-of-bounds in nilfs_direct_propagate
> after truncation
> - [PATCH v2] nilfs2: fix infinite loop in nilfs_clean_segments()
> - [PATCH] nilfs2: prevent out-of-bounds read in super root block
> parsing
> - [PATCH] nilfs2: fix BUG in nilfs_copy_dirty_pages() on dirty state
> mismatch
> 
> 

Sorry, I think it was a glitch of the email client on my side. Let me
apply the patches. I've missed it.

Thanks,
Slava.

  reply	other threads:[~2026-07-28 23:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 14:16 Ryusuke Konishi
2026-07-28  4:32 ` Ryusuke Konishi
2026-07-28 23:28   ` Viacheslav Dubeyko [this message]
2026-07-28 23:56 ` Viacheslav Dubeyko

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=61617a0287d6e0bf0914088712d0b57d2e5cec75.camel@dubeyko.com \
    --to=slava@dubeyko.com \
    --cc=konishi.ryusuke@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=syzbot+8baf9a79a3ffc6271cb6@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®