linux-kernel - Re: Allow setting of number of raw devices as a module parameter

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 for Android: free password hash cracker in your pocket

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

Message-Id: <201105031255.06410.arnd@arndb.de>
Date:	Tue, 3 May 2011 12:55:06 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Jan Kara <jack@...e.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Allow setting of number of raw devices as a module parameter

On Monday 02 May 2011, Jan Kara wrote:
> > 
> > The character device layer uses kobj_lookup internally when opening
> > the device. When you are inside the driver, you can access it through
> > file->f_path.dentry->d_inode->i_cdev, from where you go to your own data
> > structure using container_of.
>
>   OK, but if I don't have the inode of the character device (like in
> RAW_GETBIND case)?

Oh, good point. That doesn't work as easily then. You'd have to use kobj_lookup,
but you can only do that from fs/char_dev.c because otherwise the cdev_map
is not visible.

So you could in theory add a cdev_lookup() function to fs/char_dev.c, but I'm
not sure if that is a good idea if the only user is raw.c. It's probably
not any cleaner than the approach you were suggesting.

Another idea would be to make the array dynamically sized, using some version
of realloc (which doesn't exist for vmalloc today), or to use a more complex
data structure for the lookup, like idr or radix_tree.

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