From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, liushixin2@huawei.com,
konishi.ryusuke@gmail.com, chenzhongjin@huawei.com,
akpm@linux-foundation.org
Subject: [folded-merged] nilfs2-fix-nilfs_sufile_mark_dirty-not-set-segment-usage-as-dirty-v3.patch removed from -mm tree
Date: Tue, 22 Nov 2022 18:48:27 -0800 [thread overview]
Message-ID: <20221123024828.BC99AC433D6@smtp.kernel.org> (raw)
The quilt patch titled
Subject: nilfs2: Fix nilfs_sufile_mark_dirty() not set segment usage as dirty
has been removed from the -mm tree. Its filename was
nilfs2-fix-nilfs_sufile_mark_dirty-not-set-segment-usage-as-dirty-v3.patch
This patch was dropped because it was folded into nilfs2-fix-nilfs_sufile_mark_dirty-not-set-segment-usage-as-dirty.patch
------------------------------------------------------
From: Chen Zhongjin <chenzhongjin@huawei.com>
Subject: nilfs2: Fix nilfs_sufile_mark_dirty() not set segment usage as dirty
Date: Mon, 21 Nov 2022 17:11:41 +0800
add lock protection per Ryusuke
Link: https://lkml.kernel.org/r/20221121091141.214703-1-chenzhongjin@huawei.com
Fixes: 9ff05123e3bf ("nilfs2: segment constructor")
Cc: stable@vger.kernel.org
Reported-by: syzbot+77e4f005cb899d4268d1@syzkaller.appspotmail.com
Reported-by: Liu Shixin <liushixin2@huawei.com>
Signed-off-by: Chen Zhongjin <chenzhongjin@huawei.com>
Acked-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Tested-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/nilfs2/sufile.c | 2 ++
1 file changed, 2 insertions(+)
--- a/fs/nilfs2/sufile.c~nilfs2-fix-nilfs_sufile_mark_dirty-not-set-segment-usage-as-dirty-v3
+++ a/fs/nilfs2/sufile.c
@@ -499,6 +499,7 @@ int nilfs_sufile_mark_dirty(struct inode
struct nilfs_segment_usage *su;
int ret;
+ down_write(&NILFS_MDT(sufile)->mi_sem);
ret = nilfs_sufile_get_segment_usage_block(sufile, segnum, 0, &bh);
if (!ret) {
mark_buffer_dirty(bh);
@@ -509,6 +510,7 @@ int nilfs_sufile_mark_dirty(struct inode
kunmap_atomic(kaddr);
brelse(bh);
}
+ up_write(&NILFS_MDT(sufile)->mi_sem);
return ret;
}
_
Patches currently in -mm which might be from chenzhongjin@huawei.com are
nilfs2-fix-nilfs_sufile_mark_dirty-not-set-segment-usage-as-dirty.patch
reply other threads:[~2022-11-23 2:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221123024828.BC99AC433D6@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=chenzhongjin@huawei.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liushixin2@huawei.com \
--cc=mm-commits@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.