linux-kernel - Re: [PATCH] lp: implement proper detach function for parport

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <8CE2C881-7D13-4F70-8F49-D932BE4D6120@gmx.net>
Date:	Thu, 20 Jun 2013 10:25:59 +0200
From:	Hannes Weisbach <hannes_weisbach@....net>
To:	Greg Kroah-Hartman <greg@...ah.com>
Cc:	Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] lp: implement proper detach function for parport_driver lp


Am 19.06.2013 um 20:32 schrieb Greg Kroah-Hartman:
> 
>> They are doing what I am doing: translating whatever the
>> user does on a /dev/parportN-node and sending device-specific commands
>> over USB.  When they do parport_announce_port(), lp.c should also be
>> initialized and they should have the same problem.
> 
> Why hasn't anyone reported that problem then?  Surely someone must use
> these, they've been in the kernel tree for over a decade now.
I don't know.  Maybe nobody uses them (anymore/ever)?  Nobody tried to
rmmod the kernel module or compiled the driver into the kernel?

The solution to the problem (if someone encountered it) was probably
policy-based: just don't unload the module.  The comment in lp.c is
clear: /* Write this some day.  */ ;)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/