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
| ||
|
Date: Mon, 24 May 2010 09:09:31 +0900 From: Minchan Kim <minchan.kim@...il.com> To: Cesar Eduardo Barros <cesarb@...arb.net> Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org, Hugh Dickins <hughd@...gle.com> Subject: Re: [PATCH 0/3] mm: Swap checksum Hi, Cesar. I am not sure Cesar is first name. :) On Mon, May 24, 2010 at 3:32 AM, Cesar Eduardo Barros <cesarb@...arb.net> wrote: > Em 23-05-2010 11:03, Minchan Kim escreveu: >> >> On Sat, May 22, 2010 at 03:08:07PM -0300, Cesar Eduardo Barros wrote: >>> >>> Add support for checksumming the swap pages written to disk, using the >>> same checksum as btrfs (crc32c). Since the contents of the swap do not >>> matter after a shutdown, the checksum is kept in memory only. >>> >>> Note that this code does not checksum the software suspend image. >> >> We have been used swap pages without checksum. >> >> First of all, Could you explain why you need checksum on swap pages? >> Do you see any problem which swap pages are broken? > > The same reason we need checksums in the filesystem. > > If you use btrfs as your root filesystem, you are protected by checksums > from damage in the filesystem, but not in the swap partition (which is often > in the same disk, and thus as vulnerable as the filesystem). It is better to > get a checksum error when swapping in than having a silently corrupted page. Do you mean "vulnerable" is other file system or block I/O operation invades swap partition and breaks data of swap? If it is, I think it's the problem of them. so we have to fix it before merged into mainline. But I admit human being always take a mistake so that we can miss it at review time. In such case, it would be very hard bug when swap pages are broken. I haven't hear about such problem until now but it might be useful if the problem happens. (Maybe they can't notice that due to hard bug to find) But I have a concern about breaking memory which includes crc by dangling pointer. In this case, swap block is correct but it would emit crc error. Do you have an idea making sure memory includes crc is correct? Before review code, let's discuss we really need this and it's useful. -- Kind regards, Minchan Kim -- 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