public inbox for ntfs3@lists.linux.dev
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Kari Argillander <kari.argillander@gmail.com>
Cc: <ntfs3@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	<linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 2/3] fs/ntfs3: Reject mount if boot's cluster size < media sector size
Date: Tue, 28 Sep 2021 20:21:54 +0300	[thread overview]
Message-ID: <fbdcbb8f-380c-4da9-2860-a3729c75e04b@paragon-software.com> (raw)
In-Reply-To: <20210927185621.2wkznecc4jndja6b@kari-VirtualBox>



On 27.09.2021 21:56, Kari Argillander wrote:
> On Mon, Sep 27, 2021 at 06:48:00PM +0300, Konstantin Komarov wrote:
>> If we continue to work in this case, then we can corrupt fs.
>>
> 
> Should have fixes tag.
> 

The bug is in initial commit.
Do I need to write
Fixes: 82cae269cfa95 "fs/ntfs3: Add initialization of super block"
?

>> Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
>> ---
>>  fs/ntfs3/super.c | 5 +++++
>>  1 file changed, 5 insertions(+)
>>
>> diff --git a/fs/ntfs3/super.c b/fs/ntfs3/super.c
>> index 7099d9b1f3aa..193f9a98f6ab 100644
>> --- a/fs/ntfs3/super.c
>> +++ b/fs/ntfs3/super.c
>> @@ -763,9 +763,14 @@ static int ntfs_init_from_boot(struct super_block *sb, u32 sector_size,
>>  	sbi->mft.lbo = mlcn << sbi->cluster_bits;
>>  	sbi->mft.lbo2 = mlcn2 << sbi->cluster_bits;
>>  
>> +	/* Compare boot's cluster and sector. */
> 
> Pretty random obvious comment and I do not know what this does in this
> patch.
> 
>>  	if (sbi->cluster_size < sbi->sector_size)
>>  		goto out;
>>  
>> +	/* Compare boot's cluster and media sector. */
>> +	if (sbi->cluster_size < sector_size)
>> +		goto out; /* No way to use ntfs_get_block in this case. */
> 
> Usually comment should not go after line. If you take chunk from patch
> 3/3 then this is not issue.
> 
>> +
>>  	sbi->cluster_mask = sbi->cluster_size - 1;
>>  	sbi->cluster_mask_inv = ~(u64)sbi->cluster_mask;
>>  	sbi->record_size = record_size = boot->record_size < 0
>> -- 
>> 2.33.0
>>
>>
>>

  reply	other threads:[~2021-09-28 17:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 15:46 [PATCH 0/3] fs/ntfs3: Refactoring of super.c Konstantin Komarov
2021-09-27 15:47 ` [PATCH 1/3] fs/ntfs3: Fix memory leak if fill_super failed Konstantin Komarov
2021-09-27 18:40   ` Kari Argillander
2021-10-01  3:56   ` kernel test robot
2021-09-27 15:48 ` [PATCH 2/3] fs/ntfs3: Reject mount if boot's cluster size < media sector size Konstantin Komarov
2021-09-27 18:56   ` Kari Argillander
2021-09-28 17:21     ` Konstantin Komarov [this message]
2021-09-28 17:58       ` Kari Argillander
2021-09-27 15:48 ` [PATCH 3/3] fs/ntfs3: Refactoring of ntfs_init_from_boot Konstantin Komarov
2021-09-27 18:52   ` Kari Argillander

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=fbdcbb8f-380c-4da9-2860-a3729c75e04b@paragon-software.com \
    --to=almaz.alexandrovich@paragon-software.com \
    --cc=kari.argillander@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    /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