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 <linux-nilfs@vger.kernel.org>,
	syzbot+1097e95f134f37d9395c@syzkaller.appspotmail.com,
	syzbot+32c3706ebf5d95046ea1@syzkaller.appspotmail.com,
	syzkaller-bugs@googlegroups.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] nilfs2: fix issues with rename operations
Date: Sat, 11 Jan 2025 23:26:34 +0900	[thread overview]
Message-ID: <20250111143518.7901-1-konishi.ryusuke@gmail.com> (raw)
In-Reply-To: <678123bf.050a0220.216c54.000f.GAE@google.com>

Hi Andrew,

please add this series to the queue for the next merge window.

This series fixes BUG_ON check failures reported by syzbot around
rename operations, and a minor behavioral issue where the mtime of a
child directory changes when it is renamed instead of moved.

Thanks,
Ryusuke Konishi

Ryusuke Konishi (2):
  nilfs2: handle errors that nilfs_prepare_chunk() may return
  nilfs2: do not update mtime of renamed directory that is not moved

 fs/nilfs2/dir.c   | 13 ++++++++++---
 fs/nilfs2/namei.c | 39 +++++++++++++++++++++------------------
 fs/nilfs2/nilfs.h |  4 ++--
 3 files changed, 33 insertions(+), 23 deletions(-)

-- 
2.43.0


  reply	other threads:[~2025-01-11 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 13:42 [syzbot] [nilfs?] kernel BUG in nilfs_set_link syzbot
2025-01-11 14:26 ` Ryusuke Konishi [this message]
2025-01-11 14:26   ` [PATCH 1/2] nilfs2: handle errors that nilfs_prepare_chunk() may return Ryusuke Konishi
2025-01-11 14:26   ` [PATCH 2/2] nilfs2: do not update mtime of renamed directory that is not moved 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=20250111143518.7901-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=syzbot+1097e95f134f37d9395c@syzkaller.appspotmail.com \
    --cc=syzbot+32c3706ebf5d95046ea1@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®