Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261491AbTIOPru (ORCPT ); Mon, 15 Sep 2003 11:47:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261494AbTIOPru (ORCPT ); Mon, 15 Sep 2003 11:47:50 -0400 Received: from pat.uio.no ([129.240.130.16]:7109 "EHLO pat.uio.no") by vger.kernel.org with ESMTP id S261491AbTIOPrs (ORCPT ); Mon, 15 Sep 2003 11:47:48 -0400 To: russell@coker.com.au Cc: Linux Kernel Subject: Re: Oops on 2.4.22 when mounting from broken NFS server References: <200309131938.40177.russell@coker.com.au> <200309152247.20462.russell@coker.com.au> From: Trond Myklebust Date: 15 Sep 2003 11:47:46 -0400 In-Reply-To: Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning. X-UiO-MailScanner: No virus found Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 673 Lines: 12 >>>>> " " == Trond Myklebust writes: > Without a tcpdump, there's no way to know why this dumped. In > what way was the NFS server broken, and exactly how do you > expect the Linux NFS client to protect you against it? 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? 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/