On Thursday, November 19, 2015 11:39:18 AM Mark Johnston wrote:
> On Thu, Nov 19, 2015 at 09:58:45AM -0800, John Baldwin wrote:
> > On Thursday, November 19, 2015 02:04:53 PM Jonathan T. Looney wrote:
> > All of these KASSERTs are redundant. WITNESS will already warn for all of
> > these in
On 11/19/15, 12:58 PM, "John Baldwin" wrote:
>On Thursday, November 19, 2015 02:04:53 PM Jonathan T. Looney wrote:
>> This change clarifies the language of the malloc(9) man page to
>>clarify
>> the restriction against calling the malloc() family of functions
>> while in
On Thursday, November 19, 2015 02:04:53 PM Jonathan T. Looney wrote:
> Author: jtl
> Date: Thu Nov 19 14:04:53 2015
> New Revision: 291074
> URL: https://svnweb.freebsd.org/changeset/base/291074
>
> Log:
> Consistently enforce the restriction against calling malloc/free when in a
> critical
On Thu, Nov 19, 2015 at 09:58:45AM -0800, John Baldwin wrote:
> On Thursday, November 19, 2015 02:04:53 PM Jonathan T. Looney wrote:
> > Author: jtl
> > Date: Thu Nov 19 14:04:53 2015
> > New Revision: 291074
> > URL: https://svnweb.freebsd.org/changeset/base/291074
> >
> > Log:
> >
On Thu, 19 Nov 2015, Jonathan T. Looney wrote:
On 11/19/15, 12:58 PM, "John Baldwin" wrote:
Note that if you are going to document in each section 9 manpage which
APIs
are not safe to call in a critical section, you will need to update just
about every section 9 manpage. A
Author: jtl
Date: Thu Nov 19 14:04:53 2015
New Revision: 291074
URL: https://svnweb.freebsd.org/changeset/base/291074
Log:
Consistently enforce the restriction against calling malloc/free when in a
critical section.
uma_zalloc_arg()/uma_zalloc_free() may acquire a sleepable lock on the