linux-kernel - Re: Incrementing module reference count

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: <20121209115517.GA27330@liondog.tnic>
Date:	Sun, 9 Dec 2012 12:55:17 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Aaron Williams <Aaron.Williams@...ium.com>
Cc:	linux-kernel@...r.kernel.org,
	"Williams, Aaron" <Aaron.Williams@...iumnetworks.com>
Subject: Re: Incrementing module reference count

On Sat, Dec 08, 2012 at 11:17:31AM -0800, Aaron Williams wrote:
> I got it working. I designed my solution to be generic so it's not
> tied to just the at24 driver. I added a memory accessor module which
> is basically a registry. The at24 driver registers with it and then
> the Vitesse PHY driver calls it to gain access to the at24 driver.
> Only when the Vitesse driver gets the memory accessor the reference
> count for the at24 driver is incremented.

Hmm, I'm not sure you even need an additional layer because there's also
request_module(). And as long as your module is using at24, you won't
need to increment its refcount, AFAICT.

HTH.

-- 
Regards/Gruss,
    Boris.
--
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/