uhm, big problem there. It was auto-mounted, using the
/net/machinename/exportname stuff; you don't get to mention any mount
options that way..
Which, means if 2.2 ships with this bug, it's a NFS DOS attack.
Why do I consider it a DOS attack? you can kill off nfsd's with this
bug, and the only way to recover is to reboot the machine...
> Now that Alan is hacking into NFSv3, maybe these problems will go away
> before 2.2. That is, shall we say, major good news. I worry a bit less
> now, but the possibility of 2.2 going out with another poor NFS
> implementation is still real, and it's not something we really want to have
> happen.
that would be nice.. is it both server and client, or just one? and if
one, which one?
-- ------------------------+-------------------------------------------------- Thomas Davis | PDSF Project Leader tadavis@lbl.gov | (510) 486-4524 | "Only a petabyte of data this year?"- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/