- Subject: [PATCH 05/16] pstore/ram: Should zap persistent zone on unlink
- From: Anton Vorontsov <anton.vorontsov@xxxxxxxxxx>
- Date: Tue, 22 May 2012 07:17:48 -0700
- Cc: devel@xxxxxxxxxxxxxxxxxxxx, linaro-kernel@xxxxxxxxxxxxxxxx, Arnd Bergmann <arnd@xxxxxxxx>, patches@xxxxxxxxxx, Marco Stornelli <marco.stornelli@xxxxxxxxx>, Stephen Boyd <sboyd@xxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, arve@xxxxxxxxxxx, Jesper Juhl <jj@xxxxxxxxxxxxx>, John Stultz <john.stultz@xxxxxxxxxx>, Shuah Khan <shuahkhan@xxxxxxxxx>, Rebecca Schultz Zavin <rebecca@xxxxxxxxxxx>, WANG Cong <xiyou.wangcong@xxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, kernel-team@xxxxxxxxxxx, Thomas Meyer <thomas@xxxxxxxx>
- Delivered-to: devel@xxxxxxxxxxxxxxxxxxxx
- In-reply-to: <20120522141717.GA31574@lizard>
Otherwise, unlinked file will reappear on the next boot.
Reported-by: Kees Cook <keescook@xxxxxxxxxxxx>
Signed-off-by: Anton Vorontsov <anton.vorontsov@xxxxxxxxxx>
---
fs/pstore/ram.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
index 16ff733..453030f 100644
--- a/fs/pstore/ram.c
+++ b/fs/pstore/ram.c
@@ -186,6 +186,7 @@ static int ramoops_pstore_erase(enum pstore_type_id type, u64 id,
return -EINVAL;
persistent_ram_free_old(cxt->przs[id]);
+ persistent_ram_zap(cxt->przs[id]);
return 0;
}
--
1.7.9.2
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
[Video for Linux]
[Mplayer Users]
[Linux USB Devel]
[Linux Audio Users]
[Photos]
[Yosemite Photos]
[Free Singles Community]
[Linux Kernel]
[Linux SCSI]
[XFree86]
[Devices]
[Yosemite Backpacking]