From: Brian King <brking@us.ibm.com>
To: jgarzik@pobox.com
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/1] libata: Convert from module_init to subsys_initcall
Date: Wed, 08 Nov 2006 14:07:05 -0600 [thread overview]
Message-ID: <455238E9.3050301@us.ibm.com> (raw)
In-Reply-To: <200610241414.k9OEEUjd009012@d01av04.pok.ibm.com>
Jeff,
Any chance of pushing this into 2.6.19? I've been had several
people hit this oops.
Thanks,
Brian
Brian King wrote:
> When building a monolithic kernel, the load order of drivers
> does not work for SAS libata users, resulting in driver load
> failures. Convert libata to use subsys_initcall instead of
> module_init, which ensures that libata gets loaded before
> any LLDD. This is the same thing that scsi core does
> to solve the problem. The load order problem was observed on
> ipr SAS adapters and should exist for other SAS users as well.
>
> Signed-off-by: Brian King <brking@us.ibm.com>
> ---
>
> linux-2.6-bjking1/drivers/ata/libata-core.c | 2 +-
> 1 files changed, 1 insertion(+), 1 deletion(-)
>
> diff -puN drivers/ata/libata-core.c~libata_subsys_init drivers/ata/libata-core.c
> --- linux-2.6/drivers/ata/libata-core.c~libata_subsys_init 2006-10-23 16:48:15.000000000 -0500
> +++ linux-2.6-bjking1/drivers/ata/libata-core.c 2006-10-23 16:48:15.000000000 -0500
> @@ -5957,7 +5957,7 @@ static void __exit ata_exit(void)
> destroy_workqueue(ata_aux_wq);
> }
>
> -module_init(ata_init);
> +subsys_initcall(ata_init);
> module_exit(ata_exit);
>
> static unsigned long ratelimit_time;
> _
--
Brian King
eServer Storage I/O
IBM Linux Technology Center
prev parent reply other threads:[~2006-11-08 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 14:14 [PATCH 1/1] libata: Convert from module_init to subsys_initcall Brian King
2006-11-08 20:07 ` Brian King [this message]
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=455238E9.3050301@us.ibm.com \
--to=brking@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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).