| 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
| ||
|
Message-ID: <4cc25cb20801230634w2cab51c7w8d62d75ec982f132@mail.gmail.com> Date: Wed, 23 Jan 2008 22:34:57 +0800 From: rmingming <mingming.nk@...il.com> To: linux-kernel@...r.kernel.org Subject: Re: Is try_module_get buggy? > Hi rminming, > > try_module_get is designed to ensure that you don't call a function inside a > module without a reference. Like any reference function, it cannot handle > the case where the argument is invalid (or invalidated partway through the > call). > > In this case, the module pointer is usually inside a registered structure. > The pointer will be valid until the structure is unregistered, which the > calling code presumably prevents while it's doing a lookup. > > Hope that clarifies, > Rusty. > Hi Rusty, Thank you so much! I think you mean that this situation can really happen, because this is a reference function, but it is so seldom, and the common result of this situation is a kernel oops, it's not very important. Am I right? Sorry about later reply, thanks again. Best wishes, rmingming -- 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