upcall: set upcall.status on parse failure
when open parsing fails, we were still returning upcall.status==NO_ERROR, so the driver assumed the open succeeded. other operations then sent up an open_state==NULL, and crashed the daemon. when upcall_parse() returns an error, set upcall.status to notify the driver upcall_parse() prints a 'parsing of upcall <name> failed with <error>.' message on failure, so i removed redundant messages from the individual upcall parsing functions Signed-off-by: Casey Bodley <cbodley@citi.umich.edu>
This commit is contained in:
parent
a0cda354be
commit
95361423f3
9 changed files with 68 additions and 84 deletions
|
|
@ -78,8 +78,10 @@ static unsigned int WINAPI thread_main(void *args)
|
|||
}
|
||||
|
||||
status = upcall_parse(outbuf, (uint32_t)outbuf_len, &upcall);
|
||||
if (status)
|
||||
if (status) {
|
||||
upcall.status = status;
|
||||
goto write_downcall;
|
||||
}
|
||||
|
||||
#if 1 //AGLO: this is just a placeholder for a real solution. I know this variable needs a lock in a
|
||||
//normal case. However, this does not prevent us from receiving an upcall for an old mount
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue