mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Carlos Laviola <claviola@ajato.com.br>
To: linux-kernel@vger.kernel.org
Subject: Re: Weird bug in kernel (invalid operand?)
Date: Tue, 22 May 2001 23:39:47 -0300	[thread overview]
Message-ID: <20010522233947.4426a82d.claviola@ajato.com.br> (raw)
In-Reply-To: <3B0A611F.B0A554AA@uow.edu.au>
In-Reply-To: <20010521171108.2fe854ab.claviola@ajato.com.br> <3B0A611F.B0A554AA@uow.edu.au>

On Tue, 22 May 2001 22:52:47 +1000, Andrew Morton <andrewm@uow.edu.au> wrote:

> Carlos Laviola wrote:
> > 
> > invalid operand: 0000
[ ... oops here ... ]
> > Segmentation fault
> > 
> > This seems to be a bug in the kernel, maybe because the file is too big,
> > and VFAT partitions don't like that.
> 
> It used to be that fatfs would hit the second BUG() in fat_get_block()
> when a file reaches two gig.  But I can't make that happen in testing,
> because the s_maxbytes stuff restricts it to 2gig-1.  What you *should*
> have seen was `wget' locking up because of a different bug :)
> 
> Are you sure you got this with 2.4.4?  If so, please run the
> output through
> 
> 	ksymoops -m System.map < oops-text

Well, in fact, I was using 2.4.5-pre1 when I had this problem. However, since
it doesn't seem like anything within the VFAT subsystem has changed from 2.4.4
to 2.4.5-pre1, 2.4.4 is probably buggy too. The relevant output from ksymoops
is below.

>>EIP; c48fb709 <[fat]fat_get_block+5d/dc>   <=====
Code;  c48fb709 <[fat]fat_get_block+5d/dc>
00000000 <_EIP>:
Code;  c48fb709 <[fat]fat_get_block+5d/dc>   <=====
   0:   0f 0b                     ud2a      <=====
Code;  c48fb70b <[fat]fat_get_block+5f/dc>
   2:   83 c4 0c                  add    $0xc,%esp
Code;  c48fb70e <[fat]fat_get_block+62/dc>
   5:   b8 fb ff ff ff            mov    $0xfffffffb,%eax
Code;  c48fb713 <[fat]fat_get_block+67/dc>
   a:   eb 6d                     jmp    79 <_EIP+0x79> c48fb782 <[fat]fat_get_block+d6/dc>
Code;  c48fb715 <[fat]fat_get_block+69/dc>
   c:   8b 87 8c 00 00 00         mov    0x8c(%edi),%eax
Code;  c48fb71b <[fat]fat_get_block+6f/dc>
  12:   0f b7 00                  movzwl (%eax),%eax

Thanks,
Carlos.

-- 
 _ _  _| _  _  | _   . _ | _  carlos.debian.net   Debian-BR Project
(_(_|| |(_)_)  |(_|\/|(_)|(_| uin#: 981913 (icq)  debian-br.sf.net

Linux: the choice of a GNU generation - Registered Linux User #103594
Shah, shah!  Ayatollah you so!

      parent reply	other threads:[~2001-05-23  2:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-21 20:11 Carlos Laviola
2001-05-22 12:52 ` Andrew Morton
2001-05-23  2:39 ` Carlos Laviola [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=20010522233947.4426a82d.claviola@ajato.com.br \
    --to=claviola@ajato.com.br \
    --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®