linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mbuesch@freenet.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev zombies
Date: Sun, 06 Jun 2004 13:38:52 +0000	[thread overview]
Message-ID: <200406061538.53589.mbuesch@freenet.de> (raw)
In-Reply-To: <200406011914.13245.mbuesch@freenet.de>

[-- Attachment #1: Type: Text/Plain, Size: 578 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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?

> thanks,
> Kay

- --
Regards Michael Buesch  [ http://www.tuxsoft.de.vu ]



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAwx5sFGK1OIvVOP4RAmsvAJ44nS0AMWlCi/xWIMacdfB/hsfK2wCg3O87
VksGYDNITbTFdpH1NzF44A0=
=KCFA
-----END PGP SIGNATURE-----

[-- Attachment #2: udev-sighandler.diff --]
[-- Type: text/x-diff, Size: 1300 bytes --]

===== udevd.c 1.32 vs edited =====
--- 1.32/udevd.c	2004-05-21 06:13:45 +02:00
+++ edited/udevd.c	2004-06-06 15:27:05 +02:00
@@ -306,7 +306,7 @@
 	return;
 }
 
-static void sig_handler(int signum)
+asmlinkage static void sig_handler(int signum)
 {
 	int rc;
 	switch (signum) {
@@ -325,7 +325,7 @@
 			goto do_write;
 			break;
 		default:
-			dbg("unhandled signal");
+			dbg("unhandled signal: %d", signum);
 			return;
 	}
 	
===== udev.c 1.56 vs edited =====
--- 1.56/udev.c	2004-03-25 00:21:41 +01:00
+++ edited/udev.c	2004-06-06 15:27:31 +02:00
@@ -55,7 +55,7 @@
 }
 #endif
 
-static void sig_handler(int signum)
+asmlinkage 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);
 	}
 }
 
===== udev.h 1.57 vs edited =====
--- 1.57/udev.h	2004-04-01 04:12:12 +02:00
+++ edited/udev.h	2004-06-06 15:26:21 +02:00
@@ -40,6 +40,10 @@
 /* length of public data */
 #define UDEVICE_LEN (offsetof(struct udevice, bus_id))
 
+#define asmlinkage	__attribute__((regparm(0)))
+#define FASTCALL(x)	x __attribute__((regparm(3)))
+#define fastcall	__attribute__((regparm(3)))
+
 struct udevice {
 	char name[NAME_SIZE];
 	char owner[OWNER_SIZE];

  parent reply	other threads:[~2004-06-06 13:38 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 [this message]
2004-06-06 23:37 ` Kay Sievers
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=200406061538.53589.mbuesch@freenet.de \
    --to=mbuesch@freenet.de \
    --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).