netdev - Re: About the alx WoL feature

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>] [day] [month] [year] [list]

Message-ID: <1526975097.6787.4.camel@sipsolutions.net>
Date:   Tue, 22 May 2018 09:44:57 +0200
From:   Johannes Berg <johannes@...solutions.net>
To:     AceLan Kao <acelan.kao@...onical.com>
Cc:     Emily Chien <emily.chien@...onical.com>,
        Andrew Lunn <andrew@...n.ch>,
        David Miller <davem@...emloft.net>,
        Anthony Wong <anthony.wong@...onical.com>,
        netdev@...r.kernel.org, Johannes Stezenbach <js@...21.net>
Subject: Re: About the alx WoL feature

+netdev

Hi,

> Sorry to write to you directly, I'm not sure if I should CC some
> public lists, please feel free to add them if that's the right way to
> do.

I think it is, adding netdev.

> I would like to add back the alx WoL feature which is reverted by you
> 5 years ago, and we have some discussions here[1] and here[2].
[...]
> 1. https://patchwork.kernel.org/patch/10331135/
> 2. https://patchwork.kernel.org/patch/10396651/

> David Miller insists to fix the wake up issue before we can add this
> feature back,

Rightfully so!

> so I'm wondering if you still have the machine which can
> reproduce the wake up issue or know who might have the machine and
> willing to help.

I still have the machine that I initially did this development on, but
it's been purposed as my NAS so testing on it is somewhat awkward.

However, as far as I remember (why the hell are you doing this 5 years
later?!) the problem never occurred on my machine. Perhaps on Johannes
Stezenbach's machine? I don't recall, but see emails in my inbox from
him related to alx WoL.

> We can try contacting Qualcomm and/or Rivet Network to sort out the issue.

Good luck with that, heh.

johannes