public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: Chris Sykes <chris@sigsegv.plus.com>,
	greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at sched.c:564! (2.4.20, 2.4.21-pre5-ac3)
Date: Thu, 27 Mar 2003 13:35:27 +0100	[thread overview]
Message-ID: <3E82F00F.7@trash.net> (raw)
In-Reply-To: <20030327131214.1dae4005.skraw@ithnet.com>

[-- Attachment #1: Type: text/plain, Size: 480 bytes --]

The ISDN bug is fixed, i sent a patch to LKML and the Maintainer last week.
I've attached the fix again, the one in isdn_ppp.c is responsible for 
the BUG()s.

Patrick


Stephan von Krawczynski wrote:

>Hello all,
>
>I just wanted to hint that this very same BUG message appears on channel
>bundling of ISDN, too. Greg, can you give a short description for this race
>please, as I would like to find it in the ISDN-code, maybe your ideas help...
>
>Thanks,
>Stephan
>
>  
>
>  
>

[-- Attachment #2: isdn-locking-fixes.diff --]
[-- Type: text/plain, Size: 1342 bytes --]

# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
#	           ChangeSet	1.1055  -> 1.1056 
#	drivers/isdn/isdn_net.c	1.15    -> 1.16   
#	drivers/isdn/isdn_ppp.c	1.20    -> 1.21   
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/03/27	kaber@trash.net	1.1056
# [ISDN]: locking fixes
# --------------------------------------------
#
diff -Nru a/drivers/isdn/isdn_net.c b/drivers/isdn/isdn_net.c
--- a/drivers/isdn/isdn_net.c	Thu Mar 27 02:00:21 2003
+++ b/drivers/isdn/isdn_net.c	Thu Mar 27 02:00:21 2003
@@ -2831,6 +2831,7 @@
 
 			/* If binding is exclusive, try to grab the channel */
 			save_flags(flags);
+			cli();
 			if ((i = isdn_get_free_channel(ISDN_USAGE_NET,
 				lp->l2_proto, lp->l3_proto, drvidx,
 				chidx, lp->msn)) < 0) {
diff -Nru a/drivers/isdn/isdn_ppp.c b/drivers/isdn/isdn_ppp.c
--- a/drivers/isdn/isdn_ppp.c	Thu Mar 27 02:00:21 2003
+++ b/drivers/isdn/isdn_ppp.c	Thu Mar 27 02:00:21 2003
@@ -1176,7 +1176,7 @@
 	if (!lp) {
 		printk(KERN_WARNING "%s: all channels busy - requeuing!\n", netdev->name);
 		retval = 1;
-		goto unlock;
+		goto out;
 	}
 	/* we have our lp locked from now on */
 

  reply	other threads:[~2003-03-27 12:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 16:25 kernel BUG at sched.c:564! (2.4.20, 2.4.21-pre5-ac3) Chris Sykes
2003-03-26 18:52 ` Greg KH
2003-03-26 19:25   ` Chris Sykes
2003-03-26 19:34     ` Greg KH
2003-03-27 11:16       ` Chris Sykes
2003-03-27 12:12         ` Stephan von Krawczynski
2003-03-27 12:35           ` Patrick McHardy [this message]
2003-03-27 15:52             ` Stephan von Krawczynski
2003-03-27 17:45             ` Greg KH
2003-03-27 17:51               ` Patrick McHardy
2003-03-27 17:58                 ` Greg KH
2003-03-27 17:46         ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2003-03-26 16:19 Chris Sykes

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=3E82F00F.7@trash.net \
    --to=kaber@trash.net \
    --cc=chris@sigsegv.plus.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.com \
    /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