[lkml]   [2012]   [Jul]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: UIO: missing resource mapping
    Am Freitag, den 13.07.2012, 21:19 +0300 schrieb Michael S. Tsirkin:
    > UIO has the same property, doesn't it? Multiple users can
    > access device memory through sysfs.

    Indeed, that's a similar problem. I haven't tried it (yet), but this
    particular problem can maybe circumvented by using mmap with the
    MAP_PRIVATE flag. Doing so is the responsibility of the driver
    programmer (like Hans already said). Even if that mmap trick does not
    work, it is pretty much sure that a BAR is already used by another
    program, if a related kernel driver is loaded. In that case the kernel
    has a chance to avoid such BAR race conditions by not giving the
    possibility to map them to the userspace.

    Nevertheless, I'm pretty sure that the possibility via sysfs to access
    BARs, which are already managed by a kernel driver, opens the door for
    denial of service attacks.

    On the other hand, I'm quite a newbie on this topic and maybe I don't
    see the big picture here. Therefore it is up to you guys to make the
    right decision (if needed).


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2012-07-16 21:01    [W:0.022 / U:1.364 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site