From: "J. Bruce Fields" <bfields@fieldses.org>
To: Koen Wilde <koen@chillheid.nl>
Cc: Neil Brown <neilb@suse.de>,
linux-nfs@vger.kernel.org, Andy Adamson <andros@netapp.com>
Subject: Re: oops when copying a file from a nfs mount
Date: Fri, 3 Feb 2012 19:11:13 -0500 [thread overview]
Message-ID: <20120204001113.GA5320@fieldses.org> (raw)
In-Reply-To: <20120203232427.20B21405DC@mail.chillheid.nl>
On Sat, Feb 04, 2012 at 12:24:27AM +0100, Koen Wilde wrote:
> On Fri, 3 Feb 2012 18:08:11 -0500, "J. Bruce Fields" <bfields@fieldses.org> wrote:
> >
> > Is this really the start of the trace, or were there any lines before?
> >
>
> This is really the start of the trace as it appears in syslog's logs. On
> the physical screen it had some extra lines on top though (I'm typing this
> over from a photo):
>
> BUG: unable to handle kernel NULL pointer dereference at (null)
> IP: [<c01f3c00>] page_address+0x10/0xe0
> << continuing from here with the *pde line >>
>
> > But I take it you're comfortable building a kernel from source? If so,
> > getting a stable git repo, then:
> >
> > git checkout v3.2.2
> > git revert 628fc192adbaae0c6178b9015fb916ce61d72b36
> >
> > and then testing the resulting kernel--it'd be interesting to know if
> > the bug goes away.
>
> Sure, I can build a kernel from source:) I'll get back to you with the
> results.
OK, but--probably ignore my suggestion and try applying Trond's patch
instead....
(Also, I assume mainline needs it as well as v3.2.2 ?)
--b.
next prev parent reply other threads:[~2012-02-04 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 22:36 oops when copying a file from a nfs mount koen
2012-02-03 23:08 ` J. Bruce Fields
2012-02-03 23:24 ` Koen Wilde
2012-02-04 0:11 ` J. Bruce Fields [this message]
2012-02-03 23:45 ` Myklebust, Trond
2012-02-04 13:37 ` Koen Wilde
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=20120204001113.GA5320@fieldses.org \
--to=bfields@fieldses.org \
--cc=andros@netapp.com \
--cc=koen@chillheid.nl \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.