lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87r4shp9rb.fsf@devron.myhome.or.jp>
Date:	Thu, 12 Jul 2012 19:13:44 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	Namjae Jeon <linkinjeon@...il.com>
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	Ravishankar N <cyberax82@...il.com>,
	Amit Sahrawat <amit.sahrawat83@...il.com>
Subject: Re: [PATCH] fat: Support fallocate on fat.

Namjae Jeon <linkinjeon@...il.com> writes:

>> I guess, if Windows truncates the above clusters than file size, it may
>> be prefer to truncate on linux too. We really need it over umount?
>> We never know the file whether corrupted or preallocated.
>>
>> And at least for now, it would be better to put under CONFIG_FAT_FALLOC
>> or such, and warn it as unofficial way to preallocation on the
>> explanation of CONFIG_FAT_FALLOC.
>>
>> Sorry, I'm still not reviewing the detail of code yet, like locking. And
>> I'm still not convinced whether we should add this hack (unofficial way)...
> Hi OGAWA.
> Sorry for late response.
> Currently I am looking for best solution for fallocate support.
> next patch will be upated like the following.
> 1. There is no security bug.
> 2. Fix issue takes long time while preallocating.
> 3. No compatibility issue.
> Let' discuss after seeing next version's patch again.

Sure, thanks.
-- 
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ