public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: TimO <hairballmt@mcn.net>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS-kernel 2.4.3-pre1
Date: Sun, 04 Mar 2001 17:27:56 -0700	[thread overview]
Message-ID: <3AA2DD8C.E4C5628C@mcn.net> (raw)
In-Reply-To: <Pine.GSO.4.21.0103030140070.17703-100000@weyl.math.psu.edu>

Alexander Viro wrote:
> 
> On Fri, 2 Mar 2001, TimO wrote:
> 
> > eax: 00000000  ebx: 00000000  ecx: 00000000  edx: 00000000
> [snip]
> > >>EIP; c0142a52 <get_new_inode+b2/160>   <=====
> > Trace; c0142ca6 <iget4+b6/d0>
> > Trace; c0145f01 <proc_get_inode+41/120>
> > Trace; c014601a <proc_read_super+3a/b0>
> > Trace; c01349a4 <read_super+104/180>
> > Trace; c0134f7a <kern_mount+2a/80>
> > Trace; c0107007 <init+7/110>
> > Trace; c01074b8 <kernel_thread+28/40>
> > Code;  c0142a52 <get_new_inode+b2/160>
> > 00000000 <_EIP>:
> > Code;  c0142a52 <get_new_inode+b2/160>   <=====
> [snip]
> 
> Lovely. sb->s_op == NULL in iget(). The thing being, proc_read_super()
> explicitly sets ->s_op to non-NULL. Oh, and that area hadn't changed since
> 2.4.2, so I'd rather suspect the b0rken build. Can you reproduce it?
> 
>                                                         Cheers,
>                                                                 Al

Not anymore; rm -rf seems to have fixed it (make mrproper didn't). 
Guess
I should have tried that before posting.  Don't know how it got screwed
up; only 2 patches applied to this tree.

   Thanks,

===============
-- Tim

      parent reply	other threads:[~2001-03-05  1:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-03  4:34 OOPS-kernel 2.4.3-pre1 TimO
2001-03-03  6:49 ` Alexander Viro
2001-03-03  7:00   ` Alexander Viro
2001-03-05  0:27   ` TimO [this message]

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=3AA2DD8C.E4C5628C@mcn.net \
    --to=hairballmt@mcn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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