From: Marc Zyngier <mzyngier@freesurf.fr>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org,
jgarzik@pobox.com
Subject: Re: [3C509] Fix sysfs leak.
Date: Tue, 16 Mar 2004 17:05:45 +0100 [thread overview]
Message-ID: <wrpr7vseq06.fsf@panther.wild-wind.fr.eu.org> (raw)
In-Reply-To: <20040316153018.GB17958@redhat.com> (Dave Jones's message of "Tue, 16 Mar 2004 15:30:19 +0000")
>>>>> "Dave" == Dave Jones <davej@redhat.com> writes:
Dave> no it doesn't, which is the whole purpose of the patch I sent.
Dave> try it..
Dave> modprobe 3c509
Dave> lsmod | grep 3c509 # module didnt stay around
Dave> find /sys | grep 3c509 # oh look, it left crap in sysfs
Real problem, wrong fix. You just killed 3c509 EISA support
altogether. Could you please test the following patch (against latest
bk) :
===== drivers/net/3c509.c 1.49 vs edited =====
--- 1.49/drivers/net/3c509.c Mon Mar 15 22:24:30 2004
+++ edited/drivers/net/3c509.c Tue Mar 16 16:44:24 2004
@@ -1655,14 +1655,14 @@
}
#ifdef CONFIG_EISA
- if (eisa_driver_register (&el3_eisa_driver) <= 0) {
+ if (eisa_driver_register (&el3_eisa_driver) < 0) {
eisa_driver_unregister (&el3_eisa_driver);
}
#endif
#ifdef CONFIG_MCA
mca_register_driver(&el3_mca_driver);
#endif
- return el3_cards ? 0 : -ENODEV;
+ return 0;
}
static void __exit el3_cleanup_module(void)
This is not pretty either, but 3c579 probing will work, and in your
case it won't leave a dangling directory in sysfs.
Dave> Why is this even an issue so late on? Bus probing should have
Dave> been done as part of bootup. By the time I get to modprobing
Dave> device drivers, it should have been determined already.
Modprobing is perfectly OK, and indeed everything has been probed at
this stage. But having built-in drivers raises a few different
problems (the driver may be initialized before all busses are probed).
Dave> Your argument seems to be "probing is hard, so we don't do it",
Dave> which is just *wrong*.
If you want to get back to the 2.4 state, where every single EISA
driver reinvents EISA probing, fair enough. I think 2.6 has it mostly
right (at least, it respects the bus hierarchy, which is necessary to
set futile things like dma_mask correctly). Drivers may be broken
(does hp100 rings a bell ?), but the framework looks sane to me.
Again, if you have something better to offer, I'm all ears.
Regards,
M.
--
Places change, faces change. Life is so very strange.
next prev parent reply other threads:[~2004-03-16 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 21:47 davej
2004-03-16 10:56 ` Marc Zyngier
2004-03-16 13:46 ` Dave Jones
2004-03-16 14:09 ` Marc Zyngier
2004-03-16 14:29 ` Dave Jones
2004-03-16 15:05 ` Marc Zyngier
2004-03-16 15:30 ` Dave Jones
2004-03-16 16:05 ` Marc Zyngier [this message]
2004-03-16 16:16 ` Dave Jones
2004-03-16 15:58 ` Richard B. Johnson
2004-03-19 16:36 ` Vojtech Pavlik
2004-03-16 16:06 ` Jeff Garzik
2004-03-16 16:13 ` Dave Jones
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=wrpr7vseq06.fsf@panther.wild-wind.fr.eu.org \
--to=mzyngier@freesurf.fr \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®