All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+5141f6db57a2f7614352@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Re: KMSAN: uninit-value in f2fs_new_node_page()
Date: Tue, 03 Dec 2024 08:28:51 -0800	[thread overview]
Message-ID: <674f31c3.050a0220.17bd51.0048.GAE@google.com> (raw)
In-Reply-To: <674f1d49.050a0220.48a03.003b.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: Re: KMSAN: uninit-value in f2fs_new_node_page()
Author: dmantipov@yandex.ru

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git cdd30ebb1b9f36159d66f088b61aee264e649d7a

diff --git a/fs/f2fs/node.h b/fs/f2fs/node.h
index 6aea13024ac1..7371c09174cb 100644
--- a/fs/f2fs/node.h
+++ b/fs/f2fs/node.h
@@ -105,6 +105,7 @@ static inline bool get_nat_flag(struct nat_entry *ne, unsigned int type)
 
 static inline void nat_reset_flag(struct nat_entry *ne)
 {
+	ne->ni.flag = 0;
 	/* these states can be set only after checkpoint was done */
 	set_nat_flag(ne, IS_CHECKPOINTED, true);
 	set_nat_flag(ne, HAS_FSYNCED_INODE, false);
@@ -117,6 +118,7 @@ static inline void node_info_from_raw_nat(struct node_info *ni,
 	ni->ino = le32_to_cpu(raw_ne->ino);
 	ni->blk_addr = le32_to_cpu(raw_ne->block_addr);
 	ni->version = raw_ne->version;
+	ni->flag = 0;
 }
 
 static inline void raw_nat_from_node_info(struct f2fs_nat_entry *raw_ne,

  reply	other threads:[~2024-12-03 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 15:01 [f2fs-dev] [syzbot] [f2fs?] KMSAN: uninit-value in f2fs_new_node_page syzbot
2024-12-03 15:01 ` syzbot
2024-12-03 16:28 ` syzbot [this message]
2024-12-12 18:03 ` [syzbot] Re: KMSAN: uninit-value in f2fs_new_node_page() syzbot

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=674f31c3.050a0220.17bd51.0048.GAE@google.com \
    --to=syzbot+5141f6db57a2f7614352@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.