From: Gautham Gujjula <gauthamgujjula@gmail.com>
To: syzbot <syzbot+08d8956768c96a2c52cf@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] KMSAN: uninit-value in longest_match_std (2)
Date: Mon, 3 Feb 2025 01:28:59 -0600 [thread overview]
Message-ID: <Z6BwO0utCjxMG6RI@linux-dev> (raw)
In-Reply-To: <679a131a.050a0220.ac840.02d2.GAE@google.com>
#syz test
Hello,
I've been unable to reproduce the error from this patch test by running
ktest with my patch on top of 05dbaf8dd8bf ("Merge tag 'x86-urgent-2025-01-28'
of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip") and 2014c95afece
("Linux 6.14-rc1"). Since the error appears in the boot sequence before
the actual reproducer executes, I don't believe this patch is the
suspect. I'll resubmit the patch for testing, and take a deeper look if
the problem reappears.
Thanks,
Gautham Gujjula
diff --git a/fs/ntfs3/file.c b/fs/ntfs3/file.c
index fad68ff0b6ed..6fc4f960f4d9 100644
--- a/fs/ntfs3/file.c
+++ b/fs/ntfs3/file.c
@@ -1122,6 +1122,13 @@ static ssize_t ntfs_compress_write(struct kiocb *iocb, struct iov_iter *from)
}
goto out;
}
+ } else if (to & (frame_size - 1)) {
+ for (ip = to >> PAGE_SHIFT, off = offset_in_page(to);
+ ip < pages_per_frame;
+ ip++, off = 0) {
+ zero_user_segment(pages[ip], off, PAGE_SIZE);
+ flush_dcache_page(pages[ip]);
+ }
}
}
next prev parent reply other threads:[~2025-02-03 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Z5m8gtq402m-KfE2@linux-dev>
2025-01-29 11:38 ` [syzbot] [ntfs3?] KMSAN: uninit-value in longest_match_std (2) syzbot
2025-02-03 7:28 ` Gautham Gujjula [this message]
2025-02-03 8:14 ` syzbot
[not found] <CAPqLRf1KTbnuBhb=Hz8t=avYs1dp=LJp_NsObH1r53kT3udw1w@mail.gmail.com>
2025-11-19 15:36 ` syzbot
2024-01-09 18:17 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=Z6BwO0utCjxMG6RI@linux-dev \
--to=gauthamgujjula@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+08d8956768c96a2c52cf@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 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.