public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jak@rudolph.ccur.com (Joe Korty)
To: rml@tech9.net (Robert Love)
Cc: akpm@zip.com.au (Andrew Morton), linux-kernel@vger.kernel.org
Subject: [PATCH] ext3 lockup fix to lock-break-rml-2.4.18-1.patch
Date: Mon, 22 Jul 2002 20:05:11 -0400 (EDT)	[thread overview]
Message-ID: <200207230005.AAA24267@rudolph.ccur.com> (raw)
In-Reply-To: <1027362145.932.49.camel@sinai> from "Robert Love" at Jul 22, 2002 11:22:25 AM

Hi Robert,
The following patch fixes an apparent mismerge of Andrew Morton's low
latency work into the lock breaking patch.  Without this fix,
journal_commit_transaction() will loop forever, without making
forward progress, if need_resched was set on entry.

Base to which the patch was derived:

    linux.2.4.18.tar.bz2
    + sched-O1-2.4.18-pre8-K3.patch
    + preempt-kernel-rml-2.4.18-rc1-ingo-K3-1.patch
    + lock-break-rml-2.4.18-1.patch

Regards,
Joe


--- fs/jbd/commit.c.orig	Mon Jul 22 19:51:43 2002
+++ fs/jbd/commit.c	Mon Jul 22 19:52:00 2002
@@ -278,6 +278,7 @@
 			debug_lock_break(551);
 			spin_unlock(&journal_datalist_lock);
 			unlock_journal(journal);
+			unconditional_schedule();
 			lock_journal(journal);
 			spin_lock(&journal_datalist_lock);
 			continue;

  reply	other threads:[~2002-07-23  0:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-20 20:20 [PATCH] low-latency zap_page_range Robert Love
2002-07-22  5:14 ` Andrew Morton
2002-07-22 17:58   ` Robert Love
2002-07-22 18:05     ` Linus Torvalds
2002-07-22 18:22       ` Robert Love
2002-07-23  0:05         ` Joe Korty [this message]
2002-07-22 18:28       ` Robert Love
2002-07-22 18:40     ` Andrew Morton
2002-07-22 18:50       ` Robert Love

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=200207230005.AAA24267@rudolph.ccur.com \
    --to=jak@rudolph.ccur.com \
    --cc=akpm@zip.com.au \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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