[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54a8ae10-71f4-9e91-d2b7-bd4a30a8ac2a@gmail.com>
Date: Fri, 18 Aug 2023 12:04:16 +0530
From: Manas Ghandat <ghandatmanas@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Linux-kernel-mentees@...ts.linuxfoundation.org, anton@...era.com,
linkinjeon@...nel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-ntfs-dev@...ts.sourceforge.net,
syzbot+4768a8f039aa677897d0@...kaller.appspotmail.com
Subject: Re: [PATCH v4] ntfs : fix shift-out-of-bounds in ntfs_iget
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.
On 17/08/23 00:45, Greg KH wrote:
> On Sun, Aug 13, 2023 at 11:29:49AM +0530, Manas Ghandat wrote:
>> Currently there is not check for ni->itype.compressed.block_size when
>> a->data.non_resident.compression_unit is present and NInoSparse(ni) is
>> true. Added the required check to calculation of block size.
>>
>> Signed-off-by: Manas Ghandat <ghandatmanas@...il.com>
>> Reported-by: syzbot+4768a8f039aa677897d0@...kaller.appspotmail.com
>> Closes: https://syzkaller.appspot.com/bug?extid=4768a8f039aa677897d0
>> Fix-commit-ID: upstream f40ddce88593482919761f74910f42f4b84c004b
> What is this last tag for? That's a kernel release version, what can be
> done with that?
>
> confused,
>
> greg k-h
Powered by blists - more mailing lists