On Fri, Jan 23, 2015 at 05:29:46PM +, Topi Miettinen wrote:
On 01/23/15 03:06, Lennart Poettering wrote:
On Sun, 18.01.15 23:57, Topi Miettinen (toiwo...@gmail.com) wrote:
Don't use recvmsg(2) return value to check for too long packets
(it doesn't work) but MSG_TRUNC flag.
Why
On 01/23/15 17:43, Lennart Poettering wrote:
On Fri, 23.01.15 17:29, Topi Miettinen (toiwo...@gmail.com) wrote:
On 01/23/15 03:06, Lennart Poettering wrote:
On Sun, 18.01.15 23:57, Topi Miettinen (toiwo...@gmail.com) wrote:
Don't use recvmsg(2) return value to check for too long packets
On 01/23/15 03:06, Lennart Poettering wrote:
On Sun, 18.01.15 23:57, Topi Miettinen (toiwo...@gmail.com) wrote:
Don't use recvmsg(2) return value to check for too long packets
(it doesn't work) but MSG_TRUNC flag.
Why precisely doesn't this work? I mean, it will consider messages
that are
On Fri, 23.01.15 17:29, Topi Miettinen (toiwo...@gmail.com) wrote:
On 01/23/15 03:06, Lennart Poettering wrote:
On Sun, 18.01.15 23:57, Topi Miettinen (toiwo...@gmail.com) wrote:
Don't use recvmsg(2) return value to check for too long packets
(it doesn't work) but MSG_TRUNC flag.
On Sun, 18.01.15 23:57, Topi Miettinen (toiwo...@gmail.com) wrote:
Don't use recvmsg(2) return value to check for too long packets
(it doesn't work) but MSG_TRUNC flag.
Why precisely doesn't this work? I mean, it will consider messages
that are exactly as large as the buffer as too long, but
Don't use recvmsg(2) return value to check for too long packets
(it doesn't work) but MSG_TRUNC flag.
---
src/libudev/libudev-monitor.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/libudev/libudev-monitor.c b/src/libudev/libudev-monitor.c
index 484fefe..d8e551b 100644
