public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Lord <lord@sgi.com>
To: svetljo <galia@st-peter.stw.uni-erlangen.de>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: 2.4.18-rc4-aa1 XFS oopses caused by cpio
Date: Fri, 08 Mar 2002 09:59:05 -0600	[thread overview]
Message-ID: <3C88DFC9.8060907@sgi.com> (raw)
In-Reply-To: <1015580766.20800.3.camel@svetljo.st-peter.stw.uni-erlangen.de> <3C88B612.1070206@sgi.com> <3C88C9A1.5070502@st-peter.stw.uni-erlangen.de> <3C88CB1C.90203@sgi.com>

[-- Attachment #1: Type: text/plain, Size: 372 bytes --]

Stephen Lord wrote:

>>
> Ah, so you ran growfs on the filesystem, thats the key here. It looks 
> like the new code
> does not handle growfs correctly, the structure which is null is not 
> allocated in the
> expansion case. I should have a fix shortly.
>
> Steve

Hi,

Can you try and repeat with this patch, it should apply reasonably 
cleanly to the aa tree.

Steve



[-- Attachment #2: growfs.patch --]
[-- Type: text/plain, Size: 1218 bytes --]


===========================================================================
Index: linux/fs/xfs/xfs_alloc.c
===========================================================================

2234a2235,2236
> 		pag->pagb_list = kmem_zalloc(XFS_PAGB_NUM_SLOTS *
> 					sizeof(xfs_perag_busy_t), KM_SLEEP);

===========================================================================
Index: linux/fs/xfs/xfs_mount.c
===========================================================================

151,152c151,153
< 			kmem_free(mp->m_perag[agno].pagb_list,
< 			  sizeof(xfs_perag_busy_t) * XFS_PAGB_NUM_SLOTS);
---
> 			if (mp->m_perag[agno].pagb_list)
> 				kmem_free(mp->m_perag[agno].pagb_list,
> 				  sizeof(xfs_perag_busy_t) * XFS_PAGB_NUM_SLOTS);
877,881d877
< 	for (agno = 0; agno < sbp->sb_agcount; agno++) {
< 		mp->m_perag[agno].pagb_count = 0;
< 		mp->m_perag[agno].pagb_list = kmem_zalloc(XFS_PAGB_NUM_SLOTS *
< 					sizeof(xfs_perag_busy_t), KM_SLEEP);
< 	}
1066,1067c1062,1064
< 		kmem_free(mp->m_perag[agno].pagb_list,
< 		  sizeof(xfs_perag_busy_t) * XFS_PAGB_NUM_SLOTS);
---
> 		if (mp->m_perag[agno].pagb_list)
> 			kmem_free(mp->m_perag[agno].pagb_list,
> 			  sizeof(xfs_perag_busy_t) * XFS_PAGB_NUM_SLOTS);

  reply	other threads:[~2002-03-08 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-08  9:46 2.4.18-rc4-aa1 XFS oopses caused by cpio Svetoslav Slavtchev
2002-03-08 13:01 ` Stephen Lord
2002-03-08 14:24   ` svetljo
2002-03-08 14:30     ` Stephen Lord
2002-03-08 15:59       ` Stephen Lord [this message]
2002-03-10 22:19         ` Pavel Machek
2002-03-08 18:45       ` Svetoslav Slavtchev
2002-03-08 19:14         ` Martin K. Petersen

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=3C88DFC9.8060907@sgi.com \
    --to=lord@sgi.com \
    --cc=galia@st-peter.stw.uni-erlangen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.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