On Tue, Aug 04, 2015 at 12:33:04PM +0200, Christian Borntraeger wrote:
> Am 04.08.2015 um 11:20 schrieb Peter Zijlstra:
> > On Tue, Aug 04, 2015 at 09:55:48AM +0200, Christian Borntraeger wrote:
> >> kernel build bot showed a warning triggered by commit
> >> 76695af20c01 ("locking, arch: use WRITE_
Am 04.08.2015 um 11:20 schrieb Peter Zijlstra:
> On Tue, Aug 04, 2015 at 09:55:48AM +0200, Christian Borntraeger wrote:
>> kernel build bot showed a warning triggered by commit
>> 76695af20c01 ("locking, arch: use WRITE_ONCE()/READ_ONCE() in
>> smp_store_release()/smp_load_acquire()"). Turns out th
On Tue, Aug 04, 2015 at 09:55:48AM +0200, Christian Borntraeger wrote:
> kernel build bot showed a warning triggered by commit
> 76695af20c01 ("locking, arch: use WRITE_ONCE()/READ_ONCE() in
> smp_store_release()/smp_load_acquire()"). Turns out that sparse
> does not like WRITE_ONCE accessing eleme
kernel build bot showed a warning triggered by commit
76695af20c01 ("locking, arch: use WRITE_ONCE()/READ_ONCE() in
smp_store_release()/smp_load_acquire()"). Turns out that sparse
does not like WRITE_ONCE accessing elements from the (sparse)
rcu address space.
fs/afs/inode.c:448:9: sparse: incorre
4 matches
Mail list logo