um: Error handling fixes in vector drivers

Browse source

With the addition of bess support which uses connection
oriented SEQPACKET sockets the vector routines can now
encounter a "remote end closed the connection" scenario.

This adds handling code to detect it in the TX path and
the legacy RX path. There is no way to detect it in the
vector RX path because that can legitimately return 0
even if the remote end has not closed the connection. As
a result the detection is delayed until the first TX
event after the close.

Signed-off-by: Anton Ivanov <anton.ivanov@cambridgegreys.com>
Signed-off-by: Richard Weinberger <richard@nod.at>

...

This commit is contained in:

Anton Ivanov 2019-08-09 08:40:20 +01:00 • committed by Richard Weinberger

parent 5853193103

commit d47761db97

3 changed files with 35 additions and 7 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

37

arch/um/drivers/vector_kern.c

View file

1

arch/um/drivers/vector_kern.h

View file

4

arch/um/drivers/vector_user.c

View file