From mboxrd@z Thu Jan  1 00:00:00 1970
From: richard@nod.at (Richard Weinberger)
Date: Tue, 12 Nov 2013 09:50:47 +0100
Subject: Regarding enumerating Block devices registered in kernel mode
In-Reply-To: <SNT147-DS17A2287E45B507AEC6CB1BA7FE0@phx.gbl>
References: <SNT147-DS102F7B6B26489C3721C0CCA7FE0@phx.gbl>
	<CAFLxGvza7moy0ZqrFVRN3F4q0xFO_eQw+b9seCk3N5WEgrR+Hg@mail.gmail.com>
	<SNT147-DS17A2287E45B507AEC6CB1BA7FE0@phx.gbl>
Message-ID: <5281EBE7.1070007@nod.at>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

Am 12.11.2013 09:47, schrieb vaibhav:
> Thanks for replying Richard,
> 
> I need to access the blockdevice structure associated with each block device
> so that I can patch its block_device_operations to receive ioctls calls in
> my code. In my code I check for ioctls that I handle and pass it to the
> original ioctl handler if the ioctl is not understood by me.  
> 
> I intend to patch these block_device structures during my module
> initialization hence I need to iterate all BD's available in the system at
> that point. Also need to keep track of new BD's appearing in the system so
> that I can patch them as soon as they are available.

Please don't do that.
Such patching/hooking/etc...-games are doomed to failure.

Thanks,
//richard