From: Mikael Pettersson <mikpe@csd.uu.se>
To: rusty@rustcorp.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: two 2.5 modules bugs
Date: Sun, 29 Dec 2002 21:18:21 +0100 (MET) [thread overview]
Message-ID: <200212292018.VAA25446@harpo.it.uu.se> (raw)
On Sat, 28 Dec 2002 21:37:22 +1100, Rusty Russell wrote:
>> 1. With kernel 2.5.53 and module-init-tools-0.9.6, "modprobe tulip"
>> fails and goes into an infinite CPU-consuming loop. The problem
>> appears to be related to the dependency from tulip to crc32. If I
>> manually modprobe crc32 before modprobe tulip, it works. If crc32
>> isn't loaded, modprobe tulip first loads crc32 and then loops.
>>
>> module-init-tools-0.9.5 did not have this problem.
>
>This should be fixed in 0.9.6: a double free caused all kinds of wierd
>behavior. Please tell me if this fixes it.
module-init-tools-0.9.7 fixed the problem.
>Ew. I horribly misinterpreted "1-16s" to mean "a string 1-16 chars
>long". The obvious fix (untested) is:
>
>diff -urpN --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/current-dontdiff --minimal linux-2.5.53/kernel/module.c working-2.5.53-sparam/kernel/module.c
>--- linux-2.5.53/kernel/module.c 2002-12-26 15:41:06.000000000 +1100
>+++ working-2.5.53-sparam/kernel/module.c 2002-12-28 21:32:34.000000000 +1100
>@@ -604,7 +604,8 @@ extern int set_obsolete(const char *val,
> return param_array(kp->name, val, min, max, obsparm->addr,
> sizeof(long), param_set_long);
> case 's':
>- return param_string(kp->name, val, min, max, obsparm->addr);
>+ return param_array(kp->name, val, min, max, obsparm->addr,
>+ sizeof(char *), param_set_charp);
> }
> printk(KERN_ERR "Unknown obsolete parameter type %s\n", obsparm->type);
> return -EINVAL;
Tested. This patch makes the parport_pc module work again. Thanks.
/Mikael
next reply other threads:[~2002-12-29 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-29 20:18 Mikael Pettersson [this message]
2002-12-30 6:13 ` two 2.5 modules bugs Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2002-12-30 11:39 Rusty Russell
2002-12-27 16:16 Mikael Pettersson
2002-12-27 23:24 ` Petr Vandrovec
2002-12-28 10:37 ` Rusty Russell
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=200212292018.VAA25446@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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