From: Chris Wright <chrisw@osdl.org>
To: David Wilk <davidwilk@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: assertion failure in fs/jbd/checkpoint.c persists in 2.6.11.12
Date: Thu, 16 Jun 2005 11:31:29 -0700 [thread overview]
Message-ID: <20050616183129.GH9153@shell0.pdx.osdl.net> (raw)
In-Reply-To: <a4403ff605061611134318f0fb@mail.gmail.com>
* David Wilk (davidwilk@gmail.com) wrote:
> We've been plagued buy this ext3 bug since 2.6.10, and it only happens
> on heavily loaded postgres systems. We run our postgres DB on ext3
> data=journal on a dmcrypt partition. Our kernel is also patched with
> grsec, but that doesn't appear to play any role.
Can you recreate w/out grsec, and w/out dm-crypt? IOW, just ext3 plus
your load?
> After upgrading to 2.6.11.12 (specifically for the ext3 checkpoint.c
> fix) we noticed two things. The assertion failure persists, and now
> we get a condition where a postgres process will spin in state 'D'
> forever and hog 100% of a CPU (in system, not user).
>
> I've attached the trace in plain text so the formatting doesn't get screwed.
>
> Let me know if anyone would like more information. I'm no programmer,
> but I'd like to help in any way that I can.
Would you mind trying this patch:
From: Jan Kara <jack@suse.cz>
On one path, cond_resched_lock() fails to return true if it dropped the lock.
We think this might be causing the crashes in JBD's log_do_checkpoint().
(chrisw: backport to 2.6.11.12)
---
kernel/sched.c | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)
Index: release-2.6.11/kernel/sched.c
===================================================================
--- release-2.6.11.orig/kernel/sched.c
+++ release-2.6.11/kernel/sched.c
@@ -3788,11 +3788,14 @@ EXPORT_SYMBOL(cond_resched);
*/
int cond_resched_lock(spinlock_t * lock)
{
+ int ret = 0;
+
#if defined(CONFIG_SMP) && defined(CONFIG_PREEMPT)
if (lock->break_lock) {
lock->break_lock = 0;
spin_unlock(lock);
cpu_relax();
+ ret = 1;
spin_lock(lock);
}
#endif
@@ -3800,10 +3803,10 @@ int cond_resched_lock(spinlock_t * lock)
_raw_spin_unlock(lock);
preempt_enable_no_resched();
__cond_resched();
+ ret = 1;
spin_lock(lock);
- return 1;
}
- return 0;
+ return ret;
}
EXPORT_SYMBOL(cond_resched_lock);
prev parent reply other threads:[~2005-06-16 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 18:13 BUG: assertion failure in fs/jbd/checkpoint.c persists in 2.6.11.12 David Wilk
2005-06-16 18:31 ` Chris Wright [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=20050616183129.GH9153@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=davidwilk@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.