From: Christoph Hellwig <hch@infradead.org>
To: David Ford <david+cert@blue-labs.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.66 buglet
Date: Thu, 27 Mar 2003 14:54:40 +0000 [thread overview]
Message-ID: <20030327145440.A900@infradead.org> (raw)
In-Reply-To: <3E827CDA.8030904@blue-labs.org>; from david+cert@blue-labs.org on Wed, Mar 26, 2003 at 11:23:54PM -0500
On Wed, Mar 26, 2003 at 11:23:54PM -0500, David Ford wrote:
> <boot dmesg snip>
> devfs_register(cpu/microcode): illegal mode: 8180
> </snip>
>
> # ls /dev/cpu
> # grep -i microcode /boot/2.5.66/.config
> CONFIG_MICROCODE=y
>
> Not sure how it breaks between .64 where it worked and .66 where it
> doesn't. The code where it's registered doesn't appear to have changed.
> arch/i386/kernel/microcode.c, line 137.
Please try the appended patch.
--- 1.17/arch/i386/kernel/microcode.c Tue Mar 11 09:16:36 2003
+++ edited/arch/i386/kernel/microcode.c Thu Mar 27 10:24:37 2003
@@ -107,7 +107,6 @@
static char *mc_applied; /* array of applied microcode blocks */
static unsigned int mc_fsize; /* file size of /dev/cpu/microcode */
-/* we share file_operations between misc and devfs mechanisms */
static struct file_operations microcode_fops = {
.owner = THIS_MODULE,
.read = microcode_read,
@@ -122,41 +121,33 @@
.fops = µcode_fops,
};
-static devfs_handle_t devfs_handle;
-
static int __init microcode_init(void)
{
int error;
error = misc_register(µcode_dev);
if (error)
- printk(KERN_WARNING
- "microcode: can't misc_register on minor=%d\n",
- MICROCODE_MINOR);
-
- devfs_handle = devfs_register(NULL, "cpu/microcode",
- DEVFS_FL_DEFAULT, 0, 0, S_IFREG | S_IRUSR | S_IWUSR,
- µcode_fops, NULL);
- if (devfs_handle == NULL && error) {
- printk(KERN_ERR "microcode: failed to devfs_register()\n");
- misc_deregister(µcode_dev);
- goto out;
- }
- error = 0;
+ goto fail;
+ error = devfs_mk_symlink("cpu/microcode", "../misc/microcode");
+ if (error)
+ goto fail_deregister;
+
printk(KERN_INFO
"IA-32 Microcode Update Driver: v%s <tigran@veritas.com>\n",
MICROCODE_VERSION);
+ return 0;
-out:
+fail_deregister:
+ misc_deregister(µcode_dev);
+fail:
return error;
}
static void __exit microcode_exit(void)
{
misc_deregister(µcode_dev);
- devfs_unregister(devfs_handle);
- if (mc_applied)
- kfree(mc_applied);
+ devfs_remove("cpu/microcode");
+ kfree(mc_applied);
printk(KERN_INFO "IA-32 Microcode Update Driver v%s unregistered\n",
MICROCODE_VERSION);
}
next prev parent reply other threads:[~2003-03-27 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 4:23 2.5.66 buglet David Ford
2003-03-27 14:54 ` Christoph Hellwig [this message]
2003-03-27 23:30 ` Dave Jones
2003-03-28 8:26 ` Christoph Hellwig
2003-03-28 11:11 ` 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=20030327145440.A900@infradead.org \
--to=hch@infradead.org \
--cc=david+cert@blue-labs.org \
--cc=linux-kernel@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