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]
Date:	Thu, 25 Sep 2008 14:36:11 +0200
From:	Joakim Tjernlund <joakim.tjernlund@...nsmode.se>
To:	Paul Mundt <lethal@...ux-sh.org>
Cc:	Ben Nizette <bn@...sdigital.com>,
	"Hans J. Koch" <hjk@...utronix.de>, gregkh@...e.de,
	Linux-Kernel <linux-kernel@...r.kernel.org>
Subject: Re: UIO device name

On Thu, 2008-09-25 at 20:53 +0900, Paul Mundt wrote:
> On Thu, Sep 25, 2008 at 01:41:08PM +0200, Joakim Tjernlund wrote:
> > On Thu, 2008-09-25 at 20:48 +1000, Ben Nizette wrote:
> > > UIO is an interface type, not a bus type.  UIO isn't a subsystem as
> > > such, it's a user interface.  If the interface is consistent (even if
> > > the backing device is different) I don't see the problem with consistent
> > > naming.
> > 
> > Do you see a problem with letting the protocol driver choose another
> > one? Why not offer the user the chance to let the name mean something?
> > 
> This thread is still going? Amazing. Anyways, your protocol driver
> argument doesn't make any sense. Take the case of uio_pdrv or the genirq
> variant. This is the name it hands off to the core, while the devices
> that register underneath it all have their own names set. Go grep for all
> instances of uio_pdrv platform data in the architecture code. I'm getting
> the impression you haven't actually even bothered to look at the name
> entries.

Thanks for your kind words. It is true that I am not an expert in this
area, just trying to understand and improve. Obviously I still lack 
some knowledge but now I am done with uio's interface naming, I will
just scan sysfs for it. 

 Jocke
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ