Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

If we can't malloc a RF_ShutdownList then we should return ENOMEM right away.

Browse Source 
Waiting for more kernel memory to come along can cause more problems than
we're willing to deal with right now.
This commit is contained in:
oster 2000-01-13 23:41:18 +00:00
parent 1ee1632a02
commit ec84f30ddd
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
sys/dev/raidframe/rf_shutdown.c
View File

@ -1,4 +1,4 @@
/* $NetBSD: rf_shutdown.c,v 1.5 2000/01/08 22:57:31 oster Exp $ */
/* $NetBSD: rf_shutdown.c,v 1.6 2000/01/13 23:41:18 oster Exp $ */
/*
* rf_shutdown.c
*/
@ -59,7 +59,10 @@ _rf_ShutdownCreate(
* Have to directly allocate memory here, since we start up before
* and shutdown after RAIDframe internal allocation system.
*/
ent = (RF_ShutdownList_t *) malloc(sizeof(RF_ShutdownList_t), M_RAIDFRAME, M_WAITOK);
/* ent = (RF_ShutdownList_t *) malloc(sizeof(RF_ShutdownList_t),
M_RAIDFRAME, M_WAITOK); */
ent = (RF_ShutdownList_t *) malloc(sizeof(RF_ShutdownList_t),
M_RAIDFRAME, M_NOWAIT);
if (ent == NULL)
return (ENOMEM);
ent->cleanup = cleanup;