Hi Chris, unless there is something I miss but I read about that in 'Der Spiegel Online' on Wednesday
http://www.spiegel.de/netzwelt/gadgets/foreshadow-neue-angriffsmethode-trifft-intel-chips-und-cloud-dienste-a-1223289.html and the link was to this page here: https://foreshadowattack.eu/ So I don't really understand about "Cannot make this public, as the patch that caused it was due to embargo'd security fix." issue. The problem is known and I also noticed that Debian issued some Intel microcode patches which raised my awareness about a potential problem again. Sorry, maybe I miss out something here. All the best Jörg Am Samstag, 18. August 2018, 21:56:52 BST schrieb Chris Samuel: > On 18/8/18 8:47 pm, Jörg Saßmannshausen wrote: > > Hi Chris, > > Hiya, > > > these are bad news if InfiniBand will be affected here as well as > > that is what we need to use for parallel calculations. They make use > > of RMDA and if that has a problem..... well, you get the idea I > > guess. > > Oh yes, this is why I wanted to bring it to everyones attention, this > isn't just about Lustre, it's much more widespread. > > > Has anybody contacted the vendors like Mellanox or Intel regarding > > this? > > As Kilian wrote in the Lustre bug quoting his RHEL bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=1618452 > > — Comment #3 from Don Dutile <ddut...@redhat.com> — > Already reported and being actively fixed. > > Cannot make this public, as the patch that caused it was due to > embargo'd > security fix. > > This issue has highest priority for resolution. > Revert to 3.10.0-862.11.5.el7 in the mean time. > > This bug has been marked as a duplicate of bug 1616346 _______________________________________________ Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
