mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Linus Torvalds" <torvalds@osdl.org>
Cc: "Greg KH" <greg@kroah.com>, "Andrew Morton" <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] Input update for 2.6.17
Date: Tue, 27 Jun 2006 08:30:31 -0400	[thread overview]
Message-ID: <d120d5000606270530x422988a3o4b6f586d3b6650ae@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606262247040.3927@g5.osdl.org>

[-- Attachment #1: Type: text/plain, Size: 466 bytes --]

On 6/27/06, Linus Torvalds <torvalds@osdl.org> wrote:
> Greg? Dmitry?
>
> To trigger, you probably need both slab debugging _and_ spinlock debugging
> on. And perhaps just the right timings, although I've been able to do it
> three times in a row now, so it doesn't seem to be _that_ timing
> sensitive.
>

Yep, this was me. I need to activate more debug options by default...

I believe this patch will fix it. Sorry, I had to send it as an attachment.

-- 
Dmitry

[-- Attachment #2: input-fix-resetting-name.patch --]
[-- Type: text/plain, Size: 1052 bytes --]

Input: fix resetting name, phys and uniq when unregistering device

It should be done before calling class_device_unregister() because
it will destroy the device and free memory if there are no other
references to the device.

Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
---
 drivers/input/input.c |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

Index: linux/drivers/input/input.c
===================================================================
--- linux.orig/drivers/input/input.c
+++ linux/drivers/input/input.c
@@ -1033,12 +1033,13 @@ void input_unregister_device(struct inpu
 	sysfs_remove_group(&dev->cdev.kobj, &input_dev_caps_attr_group);
 	sysfs_remove_group(&dev->cdev.kobj, &input_dev_id_attr_group);
 	sysfs_remove_group(&dev->cdev.kobj, &input_dev_attr_group);
-	class_device_unregister(&dev->cdev);
 
 	mutex_lock(&dev->mutex);
 	dev->name = dev->phys = dev->uniq = NULL;
 	mutex_unlock(&dev->mutex);
 
+	class_device_unregister(&dev->cdev);
+
 	input_wakeup_procfs_readers();
 }
 EXPORT_SYMBOL(input_unregister_device);

  parent reply	other threads:[~2006-06-27 12:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26  6:35 Dmitry Torokhov
2006-06-27  6:13 ` Linus Torvalds
2006-06-27  6:37   ` Greg KH
2006-06-27 18:36     ` Linus Torvalds
2006-06-27 19:16       ` Linus Torvalds
2006-06-27 19:35         ` Linus Torvalds
2006-06-27 19:40           ` Dmitry Torokhov
2006-06-27 21:03             ` Linus Torvalds
2006-06-27 19:46           ` Marcel Holtmann
2006-06-28  4:07             ` Linus Torvalds
2006-06-28  4:36               ` Linus Torvalds
2006-06-28  7:03                 ` Jeff Garzik
2006-06-28 22:05                   ` Linus Torvalds
2006-06-28 23:03                     ` Marcel Holtmann
2006-06-28 23:40                     ` Jeff Garzik
2006-06-28 23:55                       ` Linus Torvalds
2006-06-27 19:33       ` Marcel Holtmann
2006-06-27 12:30   ` Dmitry Torokhov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-28  3:50 Dmitry Torokhov
2006-04-02  5:56 Dmitry Torokhov

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=d120d5000606270530x422988a3o4b6f586d3b6650ae@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=greg@kroah.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®