From: Paul Larson <plars@linuxtestproject.org>
To: Andrew Morton <akpm@digeo.com>
Cc: felipe_alfaro@linuxmail.org, lkml <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: 2.5.69-mm8
Date: 22 May 2003 16:19:49 -0500 [thread overview]
Message-ID: <1053638390.599.3318.camel@plars> (raw)
In-Reply-To: <20030522131434.710a0c7d.akpm@digeo.com>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On Thu, 2003-05-22 at 15:14, Andrew Morton wrote:
> Paul Larson <plars@linuxtestproject.org> wrote:
> >
> > 2.5.69-mm8 is bleeding for me. :) See bugs #738 and #739.
>
> #739 seems to be the b_committed_data race. Alex is cooking up a fix for
> that. Sorry, I didn't realise it was that easy to trigger.
>
> I'm fairly amazed about #738. The asertion at fs/jbd/transaction.c:2023
> (J_ASSERT_JH(jh, kernel_locked())) is bogus and should be removed.
Yep, a few quick tests suggest that #739 looks to be fixed by Alex's
patch, and it removes the assert from 2023, so if that's bogus then his
patch fixes that too. I did see a hang with his patch and I wasn't able
to get any output or sysrq, so I'm going to go back and try with
nmi_watchdog to see if it'll tell me anything new. I'm not sure if I
just didn't get far enough to see this without his patch, or if it comes
in the door with it though. Also a few extra "sleeping function called
from illegal context" goodies on boot with it. I'm going to get this
test kicked of right now but I'll be out until Tuesday so if it doesn't
show up again quickly I won't be seeing it until then.
Thanks,
Paul Larson
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2003-05-22 21:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 9:16 2.5.69-mm8 Andrew Morton
2003-05-22 12:05 ` 2.5.69-mm8 Philippe Gramoullé
2003-05-22 12:07 ` 2.5.69-mm8 Helge Hafting
2003-05-22 21:21 ` 2.5.69-mm8 Rudmer van Dijk
2003-05-22 14:55 ` 2.5.69-mm8 William Lee Irwin III
2003-05-22 17:13 ` 2.5.69-mm8 Alexander Hoogerhuis
2003-05-22 18:53 ` 2.5.69-mm8 Felipe Alfaro Solana
2003-05-22 19:30 ` 2.5.69-mm8 Paul Larson
2003-05-22 19:39 ` 2.5.69-mm8 Martin J. Bligh
2003-05-22 19:49 ` 2.5.69-mm8 Paul Larson
2003-05-22 21:03 ` 2.5.69-mm8 Dave Hansen
2003-05-22 20:14 ` 2.5.69-mm8 Andrew Morton
2003-05-22 21:19 ` Paul Larson [this message]
2003-05-23 6:18 ` 2.5.69-mm8 Martin J. Bligh
2003-05-23 7:03 ` 2.5.69-mm8 Dave Hansen
2003-05-23 14:32 ` 2.5.69-mm8 Martin J. Bligh
2003-05-23 15:02 ` 2.5.69-mm8 William Lee Irwin III
2003-05-23 15:31 ` 2.5.69-mm8 Martin J. Bligh
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=1053638390.599.3318.camel@plars \
--to=plars@linuxtestproject.org \
--cc=akpm@digeo.com \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox