From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261471AbTIOPiN (ORCPT ); Mon, 15 Sep 2003 11:38:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261477AbTIOPiN (ORCPT ); Mon, 15 Sep 2003 11:38:13 -0400 Received: from pat.uio.no ([129.240.130.16]:40632 "EHLO pat.uio.no") by vger.kernel.org with ESMTP id S261471AbTIOPiK (ORCPT ); Mon, 15 Sep 2003 11:38:10 -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:38:03 -0400 In-Reply-To: <200309152247.20462.russell@coker.com.au> 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 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? Cheers, Trond