From mboxrd@z Thu Jan  1 00:00:00 1970
From: Guillaume Nault <g.nault@alphalink.fr>
Subject: Re: [PATCH net] pppoe: check sockaddr length in pppoe_connect()
Date: Fri, 27 Apr 2018 18:27:36 +0200
Message-ID: <20180427162736.GI1440@alphalink.fr>
References: <387ca48810af36f2626049008a795d1adc375cb8.1524494257.git.g.nault@alphalink.fr>
 <20180427122316.GA20688@la.guarana.org>
 <20180427153906.GF1440@alphalink.fr>
 <20180427155131.GA22648@la.guarana.org>
 <20180427162424.GH1440@alphalink.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: netdev@vger.kernel.org, Michal Ostrowski <mostrows@earthlink.net>
To: Kevin Easton <kevin@guarana.org>
Return-path: <netdev-owner@vger.kernel.org>
Received: from zimbra.alphalink.fr ([217.15.80.77]:49128 "EHLO
        zimbra.alphalink.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1758556AbeD0Q1j (ORCPT
        <rfc822;netdev@vger.kernel.org>); Fri, 27 Apr 2018 12:27:39 -0400
Content-Disposition: inline
In-Reply-To: <20180427162424.GH1440@alphalink.fr>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On Fri, Apr 27, 2018 at 06:24:24PM +0200, Guillaume Nault wrote:
> exact consequences. That being said if you consider the risk is
> sufficiently low, you can always submit the patch to net-next.
Humm, forget it. I didn't see David's reply before answering.