linux-kernel - [WARNING -mm] 2.6.18-rc2-mm1 build kills /dev/null!?

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: <20060727101128.GA31920@rhlx01.fht-esslingen.de>
Date:	Thu, 27 Jul 2006 12:11:28 +0200
From:	Andreas Mohr <andi@...x01.fht-esslingen.de>
To:	Andrew Morton <akpm@...l.org>
Cc:	linux-kernel@...r.kernel.org
Subject: [WARNING -mm] 2.6.18-rc2-mm1 build kills /dev/null!?

Hello all,

for some reason a 2.6.18-rc2-mm1 build seems to kill my /dev/null device!

A simple
# make bzImage modules modules_install
managed to reduce my

crw-rw-rw-    1 root     root       1,   3 27. Jul 12:04 null

into the charred remains equivalent of

-rw-r--r--    1 root     root            0 27. Jul 12:02 null

, *twice* (I tried it the first time and had that issue,
then rebuilt the device and rebooted, same problem once build started).

Any idea why this might happen?

This did not happen with a 2.6.18-rc1-mm2 build.

A simple

rm /dev/null
mknod /dev/null c 1 3
chmod 666 /dev/null

corrects the problem, BTW.

Thanks,

Andreas Mohr
-
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/