| 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: Sat, 5 May 2007 21:12:02 +0200 (MEST) From: Jan Engelhardt <jengelh@...ux01.gwdg.de> To: Theodore Tso <tytso@....edu> cc: Bernd Schubert <bs@...eap.de>, linux-kernel@...r.kernel.org Subject: Re: mkfs.ext2 triggerd RAM corruption On May 5 2007 14:57, Theodore Tso wrote: >On Sat, May 05, 2007 at 03:36:37AM +0200, Bernd Schubert wrote: >> distribution: modified debian sarge, in which aspect is the distribution >> important for this problem? mkfs2.ext2 is supposed to write to /dev/sdaX >> and not /dev/rd/0. Stracing it and grepping for open calls shows that >> only /dev/sdaX is opened in read-write mode. > >/dev/rd/0? What's this? devfs (hint hint) naming for /dev/ram0. Jan -- - 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