linux-kernel - Re: [RFC] Rollback FS

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] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 20 Oct 2013 23:22:00 +0800
From:	jiaweiwei <jiaweiwei.xiyou@...il.com>
To:	Levente Kurusa <levex@...ux.com>
Cc:	"Theodore Ts'o" <tytso@....edu>,
	Vyacheslav Dubeyko <slava@...eyko.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Harry Wei <harryxiyou@...il.com>
Subject: Re: [RFC] Rollback FS

On Sun, Oct 20, 2013 at 9:26 PM, Levente Kurusa <levex@...ux.com> wrote:
> 2013-10-20 15:19 keltezéssel, jiaweiwei írta:
>> On Sun, Oct 20, 2013 at 9:07 PM, Levente Kurusa <levex@...ux.com> wrote:
>> [...]
>>>> A good catch. Following ideas would be suitable.
>>>>
>>>> 1, Keep the blocks or inodes by a parameter we give.
>>>> 2, Keep the blocks or inodes for several seconds.
>>> Keep them where? On the HDD? We just deleted/moved that.
>>
>> Delete/move a file with a parameter, which would keep the blocks or inodes
>> in-place. Or we would keep the blocks or inodes for several seconds.
>
> The problem with keeping the inodes/blocks for several seconds is
> that you would need to find a magic number that is not small enough,
> because if it is, then what if the user doesn't notice the problem
> during a long operation? If the magic number is big, then we waste a
> lot of space.
>
> The problem with the parameter thing is that again, all the different
> filesystems need to support that feature. We can't just tell Ext3 or JFFS2 on the VFS level,
> that 'Hey, keep those inodes in place incase someone just made himself some headache.'
>

Above you said are what we should do. Don't waste time, let me design and
implement it. I would send design document for review, thanks.


-- 
 do kernel
--
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/