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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170408.083318.370417877208769419.davem@davemloft.net>
Date:   Sat, 08 Apr 2017 08:33:18 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     kys@...rosoft.com, kys@...hange.microsoft.com
Cc:     netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        devel@...uxdriverproject.org, olaf@...fle.de, apw@...onical.com,
        jasowang@...hat.com, leann.ogasawara@...onical.comi,
        marcelo.cerri@...onical.com, sthemmin@...rosoft.com
Subject: Re: [PATCH net-next 1/1] netvsc: Initialize all channel related
 state prior to opening the channel

From: kys@...hange.microsoft.com
Date: Thu,  6 Apr 2017 14:59:21 -0700

> From: K. Y. Srinivasan <kys@...rosoft.com>
> 
> Prior to opening the channel we should have all the state setup to handle
> interrupts. The current code does not do that; fix the bug. This bug
> can result in faults in the interrupt path.
>  
> Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com>

Applied, thanks.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ