diff options
author | Brian Behlendorf <[email protected]> | 2013-06-18 10:15:33 -0700 |
---|---|---|
committer | Brian Behlendorf <[email protected]> | 2013-06-20 09:58:15 -0700 |
commit | 81eaf151071eadbb3fba74d74324a0921c5fdb5f (patch) | |
tree | 8114e84e0fcdbe5e0cb194bf1d5073842b8acc05 /scripts | |
parent | df4474f92d0b1b8d54e1914fdd56be2b75f1ff5e (diff) |
Register correct handlers in nvlist_alloc()
The non-blocking allocation handlers in nvlist_alloc() would be
mistakenly assigned if any flags other than KM_SLEEP were passed.
This meant that nvlists allocated with KM_PUSHPUSH or other KM_*
debug flags were effectively always using atomic allocations.
While these failures were unlikely it could lead to assertions
because KM_PUSHPAGE allocations in particular are guaranteed to
succeed or block. They must never fail.
Since the existing API does not allow us to pass allocation
flags to the private allocators the cleanest thing to do is to
add a KM_PUSHPAGE allocator.
Signed-off-by: Brian Behlendorf <[email protected]>
Closes zfsonlinux/spl#249
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions