The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI fixes for 2.6.0-test7
Date: Wed, 15 Oct 2003 11:24:49 -0700	[thread overview]
Message-ID: <1066242289283@kroah.com> (raw)
In-Reply-To: <10662422891492@kroah.com>

ChangeSet 1.1347.1.2, 2003/10/13 11:06:38-07:00, greg@kroah.com

PCI: fix up probe functions for synclink drivers
  
Can not be marked __init, must be marked __devinit or not at all.
If it is marked __init, then oops can happen by a user writing to the
"new_id" file from sysfs.


 drivers/char/synclink.c   |    4 ++--
 drivers/char/synclinkmp.c |    4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)


diff -Nru a/drivers/char/synclink.c b/drivers/char/synclink.c
--- a/drivers/char/synclink.c	Wed Oct 15 11:18:47 2003
+++ b/drivers/char/synclink.c	Wed Oct 15 11:18:47 2003
@@ -8020,8 +8020,8 @@
 
 #endif /* ifdef CONFIG_SYNCLINK_SYNCPPP */
 
-static int __init synclink_init_one (struct pci_dev *dev,
-				     const struct pci_device_id *ent)
+static int __devinit synclink_init_one (struct pci_dev *dev,
+					const struct pci_device_id *ent)
 {
 	struct mgsl_struct *info;
 
diff -Nru a/drivers/char/synclinkmp.c b/drivers/char/synclinkmp.c
--- a/drivers/char/synclinkmp.c	Wed Oct 15 11:18:47 2003
+++ b/drivers/char/synclinkmp.c	Wed Oct 15 11:18:47 2003
@@ -5451,8 +5451,8 @@
 }
 
 
-static int __init synclinkmp_init_one (struct pci_dev *dev,
-				       const struct pci_device_id *ent)
+static int __devinit synclinkmp_init_one (struct pci_dev *dev,
+					  const struct pci_device_id *ent)
 {
 	if (pci_enable_device(dev)) {
 		printk("error enabling pci device %p\n", dev);


  reply	other threads:[~2003-10-15 18:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 18:23 [BK PATCH] PCI fixes for 2.6.0-test7 Greg KH
2003-10-15 18:24 ` [PATCH] " Greg KH
2003-10-15 18:24   ` Greg KH [this message]
2003-10-15 18:24     ` Greg KH
2003-10-15 18:24       ` Greg KH
2003-10-15 18:24         ` 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=1066242289283@kroah.com \
    --to=greg@kroah.com \
    --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