From: Suraj Sonawane <surajsonawane0215@gmail.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
syzbot+18dd03a3fcf0ffe27da0@syzkaller.appspotmail.com
Subject: Re: [PATCH] hfs: Fix uninitialized value issue in hfs_iget
Date: Fri, 15 Nov 2024 21:22:31 +0530 [thread overview]
Message-ID: <e43ec7eb-6acf-41e3-b7f9-f0391bf4cb65@gmail.com> (raw)
In-Reply-To: <20240923180050.11158-1-surajsonawane0215@gmail.com>
On 23/09/24 23:30, SurajSonawane2415 wrote:
> Fix uninitialized value issue in hfs_iget by initializing the hfs_cat_rec
> structure in hfs_lookup.
>
> Reported-by: syzbot+18dd03a3fcf0ffe27da0@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=18dd03a3fcf0ffe27da0
> Tested-by: syzbot+18dd03a3fcf0ffe27da0@syzkaller.appspotmail.com
> Signed-off-by: SurajSonawane2415 <surajsonawane0215@gmail.com>
> ---
> fs/hfs/dir.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/hfs/dir.c b/fs/hfs/dir.c
> index b75c26045df4..3b880b3e4b4c 100644
> --- a/fs/hfs/dir.c
> +++ b/fs/hfs/dir.c
> @@ -20,7 +20,7 @@
> static struct dentry *hfs_lookup(struct inode *dir, struct dentry *dentry,
> unsigned int flags)
> {
> - hfs_cat_rec rec;
> + hfs_cat_rec rec = {0};
> struct hfs_find_data fd;
> struct inode *inode = NULL;
> int res;
I wanted to follow up on the patch I submitted. I was wondering if you
had a chance to review it and if there are any comments or feedback.
Thank you for your time and consideration. I look forward to your response.
Best regards,
Suraj Sonawane
next prev parent reply other threads:[~2024-11-15 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 18:00 SurajSonawane2415
2024-11-15 15:52 ` Suraj Sonawane [this message]
2024-11-15 17:03 ` Matthew Wilcox
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=e43ec7eb-6acf-41e3-b7f9-f0391bf4cb65@gmail.com \
--to=surajsonawane0215@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+18dd03a3fcf0ffe27da0@syzkaller.appspotmail.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®