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

Message-ID: <CABjrhvqTHkuEyQ=-xaud5Y0i3YqYcdBsm2eWrR-44V=OESWypg@mail.gmail.com>
Date:	Sun, 20 Oct 2013 15:06:33 +0800
From:	jiaweiwei <jiaweiwei.xiyou@...il.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc:	Harry Wei <harryxiyou@...il.com>
Subject: [RFC] Rollback FS

Hi all,

Recently, I just do some stupid stuffs as follows.

# mv /lib/x86_64-linux-gnu/libc.so.6  /tmp

After move "/lib/x86_64-linux-gnu/libc.so.6" away, you could not run lots
of commands, which show you some errors like this.

# ls
ls: error while loading shared libraries: libc.so.6: cannot open
shared object file: No such file or directory
# mv
mv: error while loading shared libraries: libc.so.6: cannot open
shared object file: No such file or directory
...

Because they all depend on libc.so.

You could also happen to above boring stuffs when you remove some key
files in Linux OS. Now, I have a good idea to solve above problems.

We could implement a File System to record all the operations which
send to VFS. Then when you think you have done a mistake command, you
could rollback from this File System.

This is just a RFC, I would give detail implementations. Would anyone
please give me some suggestions? Thanks very much.
--
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/