From: Jeff Layton <jlayton@redhat.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Steve French <smfrench@gmail.com>,
linux-kernel@vger.kernel.org, linux-cifs@vger.kernel.org
Subject: Re: 3.5.0-rc3 (approximately) oops on cifs mount
Date: Tue, 3 Jul 2012 15:22:03 -0400 [thread overview]
Message-ID: <20120703152203.065838cb@tlielax.poochiereds.net> (raw)
In-Reply-To: <CALCETrV=7DrqzNBLBdUVycM8471+vfA5H3Hf7-PTjanH0K8=gg@mail.gmail.com>
On Tue, 3 Jul 2012 11:59:02 -0700
Andy Lutomirski <luto@amacapital.net> wrote:
> On Mon, Jul 2, 2012 at 5:28 PM, Andy Lutomirski <luto@amacapital.net> wrote:
> > On Mon, Jul 2, 2012 at 5:21 PM, Steve French <smfrench@gmail.com> wrote:
> >> Any recreation information?
> >
> > I think it was a result of trying to mount with an incorrect password,
> > which surprises me a bit. I'll try to reproduce in a little bit.
>
> Correction: it was not a wrong password -- I mounted with the correct
> password. So far, I can't reproduce it.
>
> --Andy
>
It crashed here:
BUG_ON(cpu >= nr_cpu_ids && cpu != WORK_CPU_UNBOUND);
Very odd. Seems almost like this must be some sort of memory
corruption. The work is initialized just a little bit before it gets
queued. The only thing I can figure is that something raced in and
clobbered the work struct beforehand.
One thing you could do -- maybe disassemble get_work_gcwq() and post
the results here? Maybe from that we can see what the "cpu" value
actually was by figuring out the register that holds it?
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2012-07-03 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 0:03 Andy Lutomirski
2012-07-03 0:21 ` Steve French
2012-07-03 0:28 ` Andy Lutomirski
2012-07-03 18:59 ` Andy Lutomirski
2012-07-03 19:22 ` Jeff Layton [this message]
2012-07-03 19:37 ` Andy Lutomirski
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=20120703152203.065838cb@tlielax.poochiereds.net \
--to=jlayton@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=smfrench@gmail.com \
/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®