tech-kern archive

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

kmem_alloc(0, f)

To: tech-kern%NetBSD.org@localhost
Subject: kmem_alloc(0, f)
From: Taylor R Campbell <campbell+netbsd-tech-kern%mumble.net@localhost>
Date: Sat, 29 Jul 2017 14:04:42 +0000

Why is kmem_alloc(0, f) a panic in NetBSD?

It's not parroting Solaris -- in Solaris it's allowed, according to
the man page.  An assertion appears to have been added when ad@
implemented kmguard, but maybe there's logic deeper inside dependent
on the restriction too.

This seems like a foot-oriented panic gun, and it's been a source of
problems in the past.  Can we change it?

Follow-Ups:
- Re: kmem_alloc(0, f)
  - From: Martin Husemann

Prev by Date: MP-safe IPsec SPD
Next by Date: kmem API to allocate arrays
Previous by Thread: MP-safe IPsec SPD
Next by Thread: Re: kmem_alloc(0, f)
Indexes:

Home | Main Index | Thread Index | Old Index