linux-kernel - Re: [PATCH net-next v2] net: mvneta: set rx mode during resume if interface is running

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20170329.140945.2213903265415651654.davem@davemloft.net>
Date:   Wed, 29 Mar 2017 14:09:45 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     jszhang@...vell.com
Cc:     thomas.petazzoni@...e-electrons.com, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH net-next v2] net: mvneta: set rx mode during resume if
 interface is running

From: Jisheng Zhang <jszhang@...vell.com>
Date: Wed, 29 Mar 2017 16:47:19 +0800

> I found a bug by:
> 
> 0. boot and start dhcp client
> 1. echo mem > /sys/power/state
> 2. resume back immediately
> 3. don't touch dhcp client to renew the lease
> 4. ping the gateway. No acks
> 
> Usually, after step2, the DHCP lease isn't expired, so in theory we
> should resume all back. But in fact, it doesn't. It turns out
> the rx mode isn't resumed correctly. This patch fixes it by adding
> mvneta_set_rx_mode(dev) in the resume hook if interface is running.
> 
> Signed-off-by: Jisheng Zhang <jszhang@...vell.com>
> ---
> Since v1:
>  - rebased to the latest net-next tree and explictly mention it

Applied.