Linux NILFS development
 help / color / mirror / Atom feed
From: wuyankun <wuyankun@uniontech.com>
To: konishi.ryusuke@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-nilfs@vger.kernel.org,
	slava@dubeyko.com,
	syzbot+c37bed40868932d790e9@syzkaller.appspotmail.com,
	syzkaller-bugs@googlegroups.com, wuyankun@uniontech.com
Subject: Re: [PATCH] nilfs2: prevent double insertion of b_assoc_buffers in dirty buffer lookup
Date: Wed,  1 Jul 2026 09:53:05 +0800	[thread overview]
Message-ID: <20260701015305.970002-1-wuyankun@uniontech.com> (raw)
In-Reply-To: <CAKFNMonk0BDe3PcNdu7ZvSitO1U1TFEvj9mLXAdBK96fCnBScQ@mail.gmail.com>

Thanks a lot for the detailed investigation and for clarifying the actual root cause. 
That explanation makes sense, and I agree that the proper fix should be a bounds check 
in nilfs_ioctl_move_inode_block() rather than masking it in nilfs_lookup_dirty_data_buffers().

Please go ahead and handle the fix patch on your side. 
I appreciate the help and the clear breakdown of the issue.

  reply	other threads:[~2026-07-01  1:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25  5:26 [PATCH] nilfs2: prevent double insertion of b_assoc_buffers in dirty buffer lookup wuyankun
2026-06-25 10:43 ` Ryusuke Konishi
2026-06-30 17:55   ` Ryusuke Konishi
2026-07-01  1:53     ` wuyankun [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-06-24 19:59 [syzbot] [nilfs?] BUG: corrupted list in nilfs_lookup_dirty_data_buffers syzbot
2026-06-25  9:14 ` [PATCH] nilfs2: prevent double insertion of b_assoc_buffers in dirty buffer lookup wuyankun

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=20260701015305.970002-1-wuyankun@uniontech.com \
    --to=wuyankun@uniontech.com \
    --cc=konishi.ryusuke@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=slava@dubeyko.com \
    --cc=syzbot+c37bed40868932d790e9@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