From: Hans-Peter Jansen <hpj@urpla.net>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OOPS] with 2.4.18-pre4+linux-2.4.18-NFS_ALL
Date: Wed, 23 Jan 2002 01:50:09 +0100 [thread overview]
Message-ID: <20020123005010.14E071472@shrek.lisa.de> (raw)
In-Reply-To: <20020120164118.D587513E3@shrek.lisa.de> <20020120222722.3972B143F@shrek.lisa.de> <15435.20982.84353.824971@charged.uio.no>
In-Reply-To: <15435.20982.84353.824971@charged.uio.no>
On Monday, 21. January 2002 00:25, Trond Myklebust wrote:
> >>>>> " " == Hans-Peter Jansen <hpj@urpla.net> writes:
> > On Sunday, 20. January 2002 19:03, Trond Myklebust wrote:
> >> >>>>> " " == Hans-Peter Jansen <hpj@urpla.net> writes:
> >> >
> >> > Hi Trond et al., I can reliably reproduce this oops on my
> >> > diskless with NFS_ALL applied, but not with plain-pre4, just
> >> > by quitting one of {StarOffice,VMware}.
> >>
> >> The new version should be rid of it. It was a call to
> >> get_file() which was missing a test for a NULL argument.
> >>
> > Are you sure?
>
> I forgot the nfs_cred_file() in the line above. That too is fixed now,
> and so fsx is running fine again...
Would you like to give me a pointer to the famous fsx?
Just for the record, your actual NFS_ALL patch finally solved the problem(s),
it introduced ;-)
Many thanks.
> Cheers,
> Trond
Happy-NFS-ing-ly y'rs,
Hans-Peter
next prev parent reply other threads:[~2002-01-23 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-20 16:41 Hans-Peter Jansen
2002-01-20 18:03 ` Trond Myklebust
2002-01-20 22:27 ` Hans-Peter Jansen
2002-01-20 23:25 ` Trond Myklebust
2002-01-23 0:50 ` Hans-Peter Jansen [this message]
2002-01-23 1:18 ` Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020123005010.14E071472@shrek.lisa.de \
--to=hpj@urpla.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®