From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Robert Merrill <grievre@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS bug?
Date: Thu, 20 Apr 2006 12:41:44 -0400 [thread overview]
Message-ID: <1145551304.8136.5.camel@lade.trondhjem.org> (raw)
In-Reply-To: <b3be17f30604200937l7cfaca8evcc17f6ecd72f643e@mail.gmail.com>
On Thu, 2006-04-20 at 09:37 -0700, Robert Merrill wrote:
> we have an SMP login server we just recently switched to debian
> testing from FreeBSD and it's giving us a little trouble.
>
> it mounts its /home on a seperate machine, which is still running BSD,
> over a NIC-to-NIC 1000BASE-T link.
>
> We've found the following bug exists in 2.6.15 and .16: If a directory
> under /home is readable but not executable, a call to getdents64() on
> it will kill the process with an invalid operand error in
> __copy_from_user_ll
> has this been fixed already, and is there a patch which is readily applicable?
No idea. Can you supply us with a strace of the problem?
> we're not using the latest kernel, unfortunately, because it has lockd problems.
Care to elaborate?
Cheers,
Trond
next prev parent reply other threads:[~2006-04-20 16:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 16:37 Robert Merrill
2006-04-20 16:41 ` Trond Myklebust [this message]
[not found] ` <b3be17f30604200953i652e14a2n908f1a066ffe4e7f@mail.gmail.com>
[not found] ` <1145555789.8136.13.camel@lade.trondhjem.org>
2006-04-20 18:02 ` Robert Merrill
2006-04-20 18:10 ` Trond Myklebust
2006-04-20 18:14 ` Robert Merrill
2006-04-20 19:20 ` Trond Myklebust
2006-04-20 20:29 ` Robert Merrill
2006-04-21 7:55 ` Andrew Morton
2006-04-21 14:07 ` Trond Myklebust
2006-04-21 16:43 ` Joshua Hudson
2006-04-21 18:31 ` Andrew Morton
2006-04-21 19:34 ` Trond Myklebust
2006-04-23 7:29 ` Robert Merrill
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=1145551304.8136.5.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=grievre@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®