Re: uinput broken in 2.6.15-rc1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday 14 November 2005 00:11, Neil Brown wrote:
> 
> The 'uinput' driver doesn't work well in 2.6.15-rc1.  It
> triggers this complaint:
> 		printk(KERN_WARNING "input: device %s is statically allocated, will not register\n"
> 			"Please convert to input_allocate_device() or contact [email protected]\n",
> 			dev->name ? dev->name : "<Unknown>");
> 
> The following patch fixes it for me, but I'm not convinced it is
> correct.  I would expect it to need a special 'free' routine to match
> the special 'alloc' routine, but I couldn't easily find one.
> 

Hi,

This should work OK as long as you don't try to reuse the uinput device
because input_unregister_device frees the data structure for you and
uinput does not expect to lose part of its data structure.

I am trying to comer up with a proper fix...

-- 
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux