[Bug 96293] [BAT IVB] DMESG-WARN using smp_processor_id() in preemptible [00000000] code: usb-storage/216

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Jun 2 19:52:18 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=96293

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #3 from Chris Wilson <chris at chris-wilson.co.uk> ---
Applied to -nightly (+CI) via topic/core-for-CI:

commit 46ad020cf7e398c3001bcfe45930003aa6fe62f0
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Wed Jun 1 12:10:08 2016 +0100

    iommu: Disable preemption around use of this_cpu_ptr()

    Between acquiring the this_cpu_ptr() and using it, ideally we don't want
    to be preempted and work on another CPU's private data. this_cpu_ptr()
    checks whether or not preemption is disable, and get_cpu_ptr() provides
    a convenient wrapper for operating on the cpu ptr inside a preemption
    disabled critical section (which currently is provided by the
    spinlock). Indeed if we disable preemption around this_cpu_ptr,
    we do not need the CPU local spinlock - so long as take care that no other
    CPU is running that code as do perform the cross-CPU cache flushing and
    teardown, but that is a subject for another patch.


Should quieten our CI testing.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160602/b74e3ae1/attachment.html>


More information about the intel-gfx-bugs mailing list