xfs
[Top] [All Lists]

Re: [xfs-masters] 2.6.29-rc: kernel BUG at fs/xfs/support/debug.c:108

To: "Dave Chinner" <david@xxxxxxxxxxxxx>, "Christoph Hellwig" <hch@xxxxxxxxxxxxx>, xfs-masters@xxxxxxxxxxx, xfs@xxxxxxxxxxx, kernel-testers@xxxxxxxxxxxxxxx
Subject: Re: [xfs-masters] 2.6.29-rc: kernel BUG at fs/xfs/support/debug.c:108
From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
Date: Mon, 12 Jan 2009 03:48:13 +0300
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=2dNfTEqdMcZqggnRdCn2EZILYdHyU0KVSvYkzD8WelM=; b=pcc/uwlInOEWwq5yAjvSD63Y80o7ODr1MiKVoP3k2Jsu7nSTWYDYSRwoAPbljunWq3 7NxPjij2iwgyGuuR7olgEzviqUNZGs24n5VqlQ+727z3XOurDxnKEK5AWBAJTZPJUfCU 23KpOnGLOVPA1jvMQWNj+xyBm434qqZWbvGsk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=jkiSPZad0921SWqSNYQR/8AZDB/kZwWE27y6Txt04Gmd6DOtdaXQYLvhGsIK80r14B /suk8B40Ti2gbLwKjYOVizYtlKJ/YsjkVbhTJEjsObe+vLnPLZCPI3uTdJJvMQVv7Ptz RKGkBmbS4BzGVpclnNc3z+Cc9rhZ6a3lX2fVc=
In-reply-to: <20090111104659.GB8071@disturbed>
References: <20090109044121.GA31280@orion> <a4423d670901091353s7ff12207gcb38eb093d77d401@mail.gmail.com> <a4423d670901091418j5c7fdfb2oeba2f4640f8e29d0@mail.gmail.com> <a4423d670901091511y68a53808rfaab8148526224c6@mail.gmail.com> <a4423d670901100419s2ae106bexac1a538caf654153@mail.gmail.com> <20090110143924.GA25900@infradead.org> <a4423d670901100709v1e7ce0bfs167547c5001787ac@mail.gmail.com> <20090110152803.GA7469@infradead.org> <20090110221459.GA8873@orion> <20090111104659.GB8071@disturbed>
> Hmmmm - this might be getting closer to the source of the bug.
> It's being detecting when reading in the buffer to do a left shift
> now, not during the delete of a record.
>
> I'd suggest that you treat this as the same failure and continue
> the bisect to try to find when no problems show up at all.

687b890a184fef263ebb773926e1f4aa69240d01 is the first bad commit.
Does it make sense?
It can not be reverted from the current git to be sure it is guilty
due to merge conflicts.

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