lkml.org 
[lkml]   [2003]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: Oops on 2.4.22 when mounting from broken NFS server
From
>>>>> " " == Russell Coker <russell@coker.com.au> writes:

> I expect the NFS client to behave sensibly in the face of all
> possible server errors, including the possibility of a hostile
> NFS server.

No can do... There are 100s of scenarios where the server can screw
the client by giving it bogus information. You might possibly be able
to protect against a few of them, but at a heavy price in the form of
code bloat.
Neither NFSv2 nor NFSv3 are protocols that were designed to operate
safely in a hostile environment. They were designed for LANs where
servers and clients trust one another.

I agree that we shouldn't Oops though.

>> BTW: that Oops you posted looked very much like a memory
>> corruption problem. Were you running vanilla 2.4.22 on the
>> client, or was it too patched?

> It was also patched. I will try and reproduce the error with
> an unpatched kernel and a tcpdump running.

Please do...

Cheers,
Trond
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:48    [W:0.035 / U:0.268 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site