All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger.kernel@dilger.ca>
To: Christian Casteyde <casteyde.christian@free.fr>
Cc: linux-ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access
Date: Mon, 11 Oct 2010 14:43:58 -0600	[thread overview]
Message-ID: <CBEC43EB-8CCC-40A4-85A7-4F130BAE7670@dilger.ca> (raw)
In-Reply-To: <201010021642.o92Ggp1A007965@demeter1.kernel.org>


On 2010-10-02, at 09:42, Theodore Tso <tytso@mit.edu> wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=17361
> 
> Except for the initial bug report, none of the other stack traces have anything to do with ext4/jbd2.    And in the initial ext4 trace, we see the complaint that we're calling might_sleep() in ext4_mark_inode_dirty(), in a code path where we are manifestly not taking any spinlocks.    And in fact we don't see any spinlocks being taken at the point where the complaint is mode in ext4_mark_inode_dirty().   Yet preempt_count > 1.

In my experience, this is typically caused by stack overflow smashing the task struct and randomly setting preempt_count to a non-zero value.

Cheers, Andreas






  reply	other threads:[~2010-10-11 20:47 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-29 20:00 [Bug 17361] New: Watchdog detected hard LOCKUP in jbd2_journal_get_write_access bugzilla-daemon
2010-09-07 22:05 ` [Bug 17361] " bugzilla-daemon
2010-09-07 22:27 ` bugzilla-daemon
2010-09-14  5:48 ` bugzilla-daemon
2010-09-14  5:51 ` bugzilla-daemon
2010-09-14 18:08 ` bugzilla-daemon
2010-09-21 17:19 ` bugzilla-daemon
2010-09-22 17:48 ` bugzilla-daemon
2010-09-22 17:51 ` bugzilla-daemon
2010-09-22 17:53 ` bugzilla-daemon
2010-09-22 17:56 ` bugzilla-daemon
2010-09-22 17:58 ` bugzilla-daemon
2010-09-22 18:01 ` bugzilla-daemon
2010-09-22 18:11 ` bugzilla-daemon
2010-09-22 18:13 ` bugzilla-daemon
2010-09-27 19:26 ` bugzilla-daemon
2010-10-02 16:42 ` bugzilla-daemon
2010-10-11 20:43   ` Andreas Dilger [this message]
2010-10-04 18:48 ` bugzilla-daemon
2010-10-04 18:51 ` [Bug 17361] Random kmemcheck errors and kernel freeze on 2.6.36-rc* bugzilla-daemon
2010-10-10 19:19 ` bugzilla-daemon
2010-10-10 19:20 ` bugzilla-daemon
2010-10-10 19:22 ` bugzilla-daemon
2010-10-10 19:38 ` bugzilla-daemon
2010-10-20 20:10 ` bugzilla-daemon
2010-10-20 20:38 ` bugzilla-daemon
2010-09-12 18:11 2.6.36-rc3-git5: Reported regressions from 2.6.35 Rafael J. Wysocki
2010-09-12 18:14 ` [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access Rafael J. Wysocki
2010-09-12 18:14   ` Rafael J. Wysocki
2010-09-20 18:47 2.6.36-rc4-git5: Reported regressions from 2.6.35 Rafael J. Wysocki
2010-09-20 19:08 ` [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access Rafael J. Wysocki
2010-09-20 19:08   ` Rafael J. Wysocki
2010-09-26 19:55 2.6.36-rc5-git7: Reported regressions from 2.6.35 Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access Rafael J. Wysocki
2010-10-02 16:52   ` Ted Ts'o
2010-10-02 16:52     ` Ted Ts'o
2010-10-03 11:21     ` Vegard Nossum
2010-10-03 11:21       ` Vegard Nossum
2010-10-03 21:15 2.6.36-rc6-git2: Reported regressions from 2.6.35 Rafael J. Wysocki
2010-10-03 21:19 ` [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access Rafael J. Wysocki

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=CBEC43EB-8CCC-40A4-85A7-4F130BAE7670@dilger.ca \
    --to=adilger.kernel@dilger.ca \
    --cc=casteyde.christian@free.fr \
    --cc=linux-ext4@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.