linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev zombies
Date: Sun, 06 Jun 2004 23:37:19 +0000	[thread overview]
Message-ID: <20040606233719.GA16551@vrfy.org> (raw)
In-Reply-To: <200406011914.13245.mbuesch@freenet.de>

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

On Sun, Jun 06, 2004 at 03:38:52PM +0200, Michael Buesch wrote:
> On Sunday 06 June 2004 15:16, you wrote:
> > It would be great, if you are able to test it another time with the reenabled
> > regparms.
> 
> The attached patch fixes the whole stuff for me.
> I imported some macros from the kernel. Ok, or do
> you prefer other macro-names?

> +#define asmlinkage	__attribute__((regparm(0)))
> +#define FASTCALL(x)	x __attribute__((regparm(3)))
> +#define fastcall	__attribute__((regparm(3)))

Hmm, I prefer no macro at all.

Greg, here is the usual bk text:
===
fix udevd zombies

The recent version of klibc switched to -mregparm=3. This broke the
signal handlers parameter, cause it is called directly from the kernel
with the parameter on the stack not in a register.
===

thanks,
Kay

[-- Attachment #2: 01-udev-regparm-fix.patch --]
[-- Type: text/plain, Size: 1124 bytes --]

===== udev.c 1.56 vs edited =====
--- 1.56/udev.c	Thu Mar 25 00:21:41 2004
+++ edited/udev.c	Mon Jun  7 00:49:17 2004
@@ -55,7 +55,7 @@
 }
 #endif
 
-static void sig_handler(int signum)
+__attribute__((regparm(0))) static void sig_handler(int signum)
 {
 	switch (signum) {
 		case SIGINT:
@@ -63,7 +63,7 @@
 			udevdb_exit();
 			exit(20 + signum);
 		default:
-			dbg("unhandled signal");
+			dbg("unhandled signal %d", signum);
 	}
 }
 
@@ -128,7 +128,7 @@
 		goto exit;
 	}
 
-	/* set up a default signal handler for now */
+	/* set signal handlers */
 	act.sa_handler = sig_handler;
 	sigemptyset (&act.sa_mask);
 	act.sa_flags = SA_RESTART;
===== udevd.c 1.32 vs edited =====
--- 1.32/udevd.c	Fri May 21 06:13:45 2004
+++ edited/udevd.c	Mon Jun  7 00:50:03 2004
@@ -306,9 +306,10 @@
 	return;
 }
 
-static void sig_handler(int signum)
+__attribute__((regparm(0))) static void sig_handler(int signum)
 {
 	int rc;
+
 	switch (signum) {
 		case SIGINT:
 		case SIGTERM:
@@ -325,7 +326,7 @@
 			goto do_write;
 			break;
 		default:
-			dbg("unhandled signal");
+			dbg("unhandled signal %d", signum);
 			return;
 	}
 	

  parent reply	other threads:[~2004-06-06 23:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01 17:14 udev zombies Michael Buesch
2004-06-02 16:53 ` Greg KH
2004-06-02 18:26 ` Michael Buesch
2004-06-03  8:24 ` Harald Hoyer
2004-06-03  8:27 ` Harald Hoyer
2004-06-03  8:54 ` jnf
2004-06-04  1:45 ` jnf
2004-06-04  8:03 ` Kay Sievers
2004-06-04  8:36 ` jnf
2004-06-04  8:39 ` jnf
2004-06-04  9:32 ` Kay Sievers
2004-06-04 17:23 ` jnf
2004-06-06 10:08 ` Michael Buesch
2004-06-06 10:52 ` Kay Sievers
2004-06-06 11:16 ` Michael Buesch
2004-06-06 13:16 ` Kay Sievers
2004-06-06 13:38 ` Michael Buesch
2004-06-06 23:37 ` Kay Sievers [this message]
2004-06-07  2:20 ` Greg KH

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=20040606233719.GA16551@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).