Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Sun, 29 Apr 2018 21:34:17 -0400 (EDT)
Message-Id: <20180429.213417.1622456092178936722.davem@davemloft.net>
To:     edumazet@google.com
Cc:     netdev@vger.kernel.org, luto@kernel.org,
        linux-kernel@vger.kernel.org, linux-mm@kvack.org,
        ka-cheong.poon@oracle.com, eric.dumazet@gmail.com
Subject: Re: [PATCH v4 net-next 0/2] tcp: mmap: rework zerocopy receive
From:   David Miller <davem@davemloft.net>
In-Reply-To: <20180427155809.79094-1-edumazet@google.com>
References: <20180427155809.79094-1-edumazet@google.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

From: Eric Dumazet <edumazet@google.com>
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 changes mmap()
> behavior.
> 
> Second patch changes tcp_mmap reference program.
> 
> v4: tcp mmap() support depends on CONFIG_MMU, as kbuild bot told us.
> 
> v3: change TCP_ZEROCOPY_RECEIVE to be a getsockopt() option
>     instead of setsockopt(), feedback from Ka-Cheon Poon
> 
> v2: Added a missing page align of zc->length in tcp_zerocopy_receive()
>     Properly clear zc->recv_skip_hint in case user request was completed.

Looks great, series applied, thanks Eric.