xfs
[Top] [All Lists]

Re: Kernel oops in XFS, kernel 2.6.4

To: Rens Houben <shadur@xxxxxxxxxxxxxxxxxxx>
Subject: Re: Kernel oops in XFS, kernel 2.6.4
From: Steve Lord <lord@xxxxxxx>
Date: Sun, 21 Mar 2004 08:02:29 -0600
Cc: linux-xfs@xxxxxxxxxxx, kaos@xxxxxxx
In-reply-to: <27377.1079834264@ocs3.ocs.com.au>
References: <27377.1079834264@ocs3.ocs.com.au>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.5 (X11/20040208)
Keith Owens wrote:
> On Sat, 20 Mar 2004 12:09:31 +0100, 
> Rens Houben <shadur@xxxxxxxxxxxxxxxxxxx> wrote:
> 
>>Mar 20 11:14:56 seiryuu kernel: Unable to handle kernel paging request at 
>>virtual address 6b6b6d57
>>Mar 20 11:14:56 seiryuu kernel: eax: 6b6b6b6b   ebx: 6b6b6b6b   ecx: e33a5270 
>>  edx: 00000001
> 
> 
> Repeated 0x6b is POISON_FREE.  A slab has been used after being freed.
> 

Which is somewhat scary, the oops happened here;


void
xfs_trans_unlocked_item(
         xfs_mount_t     *mp,
         xfs_log_item_t  *lip)
{
         xfs_log_item_t  *min_lip;

         /*
          * If we're forcibly shutting down, we may have
          * unlocked log items arbitrarily. The last thing
          * we want to do is to move the tail of the log
          * over some potentially valid data.
          */
         if (!(lip->li_flags & XFS_LI_IN_AIL) ||
             XFS_FORCED_SHUTDOWN(mp)) {
                ^^^^^^^^^^^^^^^^^^^
                 return;
         }

Which makes it look like the mount structure has been freed.

I notice the kernel is tainted, what was loaded?

Steve


<Prev in Thread] Current Thread [Next in Thread>