[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230522-karotten-biotechnologie-aa6ce3707ca4@brauner>
Date: Mon, 22 May 2023 12:56:52 +0200
From: Christian Brauner <brauner@...nel.org>
To: 侯伟桃 Vincent Hou <houweitao@...iglobal.com>
Cc: "syzbot+92ef9ee419803871020e@...kaller.appspotmail.com"
<syzbot+92ef9ee419803871020e@...kaller.appspotmail.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"glider@...gle.com" <glider@...gle.com>,
"keescook@...omium.org" <keescook@...omium.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"syzkaller-bugs@...glegroups.com" <syzkaller-bugs@...glegroups.com>
Subject: Re: [syzbot] [hfs?] KMSAN: uninit-value in hfsplus_listxattr
On Mon, May 22, 2023 at 10:12:38AM +0000, 侯伟桃 Vincent Hou wrote:
> Since the strbuf in hfsplus_listxattr was allocated with kmalloc and filled with hfsplus_uni2asc,
> which did not fill "\0" in last byte, in some cases, the uninited byte may be accessed when
> compare the strbuf with known namespace. But I still need check the value of xattr in strbuf
> to confirm the root cause. Please help test with below debug patch.
Uhm, no... The fs maintainers aren't responsible for testing random
debug patches sent to the list. This thing is also orphaned so the
chance of someone doing the work for you is drastically close to zero.
Powered by blists - more mailing lists