From: Manas Ghandat <ghandatmanas@gmail.com>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Linux-kernel-mentees@lists.linuxfoundation.org, anton@tuxera.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net,
syzbot+4768a8f039aa677897d0@syzkaller.appspotmail.com
Subject: Re: [PATCH v4] ntfs : fix shift-out-of-bounds in ntfs_iget
Date: Mon, 28 Aug 2023 22:22:45 +0530 [thread overview]
Message-ID: <3216b72e-76d9-368b-a903-cd3acee96438@gmail.com> (raw)
In-Reply-To: <CAKYAXd9-NjSjt-TrJ6fYcPDHcaUm-L=-h5OU98DTw97J2qwmXA@mail.gmail.com>
I was looking at this issue for some time now. As suggested by Anton,
that the vol->sparse_compression_unit is set at the mount. I cannot seem
to find the code for that part. It seems that the ntfs_inode struct does
not have any sparse_compression_unit. So I am stuck at that part of the
problem.
On 28/08/23 08:30, Namjae Jeon wrote:
> 2023-08-18 15:34 GMT+09:00, Manas Ghandat <ghandatmanas@gmail.com>:
>> Sorry for the last reply Greg. The last tag specifies the commit id.
>> Also, I have sent the v5 of the patch in which I have made some critical
>> changes. Please take a look at that.
> Have you checked build error report from kernel test robot ?
prev parent reply other threads:[~2023-08-28 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 5:59 [PATCH v4] ntfs : fix shift-out-of-bounds in ntfs_iget Manas Ghandat
2023-08-14 1:02 ` Namjae Jeon
2023-08-16 19:15 ` Greg KH
2023-08-18 6:34 ` Manas Ghandat
2023-08-28 3:00 ` Namjae Jeon
2023-08-28 16:52 ` Manas Ghandat [this message]
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=3216b72e-76d9-368b-a903-cd3acee96438@gmail.com \
--to=ghandatmanas@gmail.com \
--cc=Linux-kernel-mentees@lists.linuxfoundation.org \
--cc=anton@tuxera.com \
--cc=gregkh@linuxfoundation.org \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=syzbot+4768a8f039aa677897d0@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;
as well as URLs for NNTP newsgroup(s).