> On Sat, Nov 24, 2001 at 04:39:15PM -0200, Marcelo Tosatti wrote:
>
> > - Correctly sync inodes in iput() (Alexander Viro)
>
> Given the fact that this bug in a presumably stable linux kernel is
> getting quite some attention in the media (electronic and otherwise). It
> would be prudent to get out a 2.4.16 which fixes this bug right about
> now.
BTW, what is the correct recovery strategy, assuming 2.4.15 has not
been rebooted yet? Installing a fixed kernel is obviously the first
step. How should one reboot the system to minimize damage? Use a
normal system shutdown (with the -F parameter to forc fsck on next
boot), or go to single user, "touch /forcefsck", sync, wait a minute,
and switching of power?
-- Florian Weimer Florian.Weimer@RUS.Uni-Stuttgart.DE University of Stuttgart http://cert.uni-stuttgart.de/ RUS-CERT +49-711-685-5973/fax +49-711-685-5898 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/