Re: Adding reentrancy information to safety notes?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Dec 31, 2014, "Carlos O'Donell" <carlos@xxxxxxxxxx> wrote:

> That is not the definition of reentrancy that I had in mind.

Since reentrant is such an overloaded term, how about using the term
Recursion-Safe, that AFAICT covers only the concept you have in mind.
Another possible term that occurs to me is Synchronously Reentrant, to
indicate it doesn't cover asynchronous reentrancy out of signals or
multiple threads.  We could then shorten it as SR-Safe.

-- 
Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist|Red Hat Brasil GNU Toolchain Engineer
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux