lkml.org 
[lkml]   [2018]   [Feb]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRE: [PATCH 1/2] fs/efivarfs: restrict inode permissions
    Date
    >> EFI[1] stinks. Reading any file in /sys/firmware/efi/efivars/ generates
    >> 4 (yes FOUR!) SMIs.

    > Is that actualkly the normal implementation?

    I don't know if there are other implementations. This is what I see on my
    lab system.

    > Also, if these are just synchronous SMI's, then don't we just end up
    > correctly assigning the CPU load to the reader, and it doesn't
    > actually matter? Where's the DoS?

    SMI are broadcast to all logical CPUs. The bigger the system the
    more the pain from an SMI as code tries to rendezvous them all
    (4 socket * 24 core * 2 HyperThreads = 192 CPUs on my system).

    Looping reading files from efivarfs doesn't stop the system, but it
    does slow to a crawl while it is happening. Not a full blown DoS,
    but fairly unpleasant.

    -Tony
    \
     
     \ /
      Last update: 2018-02-21 02:06    [W:3.030 / U:1.840 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site