Fix for quite a special case when userland emulates a netgraph node, and
userland can reply to a message with NGM_HASREPLY bit set. In this case we should not wait for a response to a responce. PR: 176771 Submitted by: Keith Reynolds <keith.reynolds tidalscale.com>
This commit is contained in:
parent
6feb84d64e
commit
15e6f8c02a
@ -234,7 +234,7 @@ NgDeliverMsg(int cs, const char *path,
|
||||
}
|
||||
|
||||
/* Wait for reply if there should be one. */
|
||||
if (msg->header.cmd & NGM_HASREPLY) {
|
||||
if (msg->header.cmd & NGM_HASREPLY && !(msg->header.flags & NGF_RESP)) {
|
||||
struct pollfd rfds;
|
||||
int n;
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user