Re: [PATCH v4 net-next 0/2] tcp: mmap: rework zerocopy receive

2018-04-29 Thread David Miller
From: Eric Dumazet Date: Fri, 27 Apr 2018 08:58:07 -0700 > syzbot reported a lockdep issue caused by tcp mmap() support. > > I implemented Andy Lutomirski nice suggestions to resolve the > issue and increase scalability as well. > > First patch is adding a new getsockopt()

Re: [PATCH v4 net-next 0/2] tcp: mmap: rework zerocopy receive

2018-04-29 Thread David Miller
From: Eric Dumazet Date: Fri, 27 Apr 2018 08:58:07 -0700 > syzbot reported a lockdep issue caused by tcp mmap() support. > > I implemented Andy Lutomirski nice suggestions to resolve the > issue and increase scalability as well. > > First patch is adding a new getsockopt() operation and

[PATCH v4 net-next 0/2] tcp: mmap: rework zerocopy receive

2018-04-27 Thread Eric Dumazet
syzbot reported a lockdep issue caused by tcp mmap() support. I implemented Andy Lutomirski nice suggestions to resolve the issue and increase scalability as well. First patch is adding a new getsockopt() operation and changes mmap() behavior. Second patch changes tcp_mmap reference program.

[PATCH v4 net-next 0/2] tcp: mmap: rework zerocopy receive

2018-04-27 Thread Eric Dumazet
syzbot reported a lockdep issue caused by tcp mmap() support. I implemented Andy Lutomirski nice suggestions to resolve the issue and increase scalability as well. First patch is adding a new getsockopt() operation and changes mmap() behavior. Second patch changes tcp_mmap reference program.