search for: racey

Hi, What does this error mean? Sep 7 17:15:54 racey puppet-agent[3291]: (/Stage[main]/Sysctl/Sysctl[kernel.shmmax]) Could not evaluate: No ability to determine if sysctl exists I don''t know where to start looking. If I should post my configuration, please let me know. Best regards, Martijn.

I foolishly made the following typo: " disk = [ ''phy:/dev/vg00/virt-smtp1-root,0301,w'', ''phy:/dev/vg00/virt-smtp1-root,0302,w'' ] " instead of: " disk = [ ''phy:/dev/vg00/virt-smtp1-root,0301,w'', ''phy:/dev/vg00/virt-smtp1-swap,0302,w'' ]" (the type was that the same Dom0 block device is used twice in the

...encing a nullptr somewhere in ``fuzzer::PrintHexArray()`` which ASan then catches but then the handler for the ASan detected nullptr derefence calls ``fuzzer::PrintHexArray()`` again and so we get stuck in a loop. Some how we are managing to break out of this loop but I'm guessing this probably racey which would probably also explain the very variable timings I've been seeing for test execution. [1] http://reviews.llvm.org/D20706 Dan. -------------- next part -------------- A non-text attachment was scrubbed... Name: crash-log.txt.xz Type: application/octet-stream Size: 41200 bytes Desc:...

...ewhere in ``fuzzer::PrintHexArray()`` which ASan then catches but > then the handler for the ASan detected nullptr derefence calls > ``fuzzer::PrintHexArray()`` again and so we get stuck in a loop. Some > how we are managing to break out of this loop but I'm guessing this > probably racey which would probably also explain the very variable > timings I've been seeing for test execution. > > > [1] http://reviews.llvm.org/D20706 > > Dan. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-de...

From: Jason Gunthorpe <jgg at mellanox.com> This converts one of the two users of mmu_notifiers to use the new API. The conversion is fairly straightforward, however the existing use of notifiers here seems to be racey. Cc: Mike Marciniszyn <mike.marciniszyn at intel.com> Cc: Dennis Dalessandro <dennis.dalessandro at intel.com> Signed-off-by: Jason Gunthorpe <jgg at mellanox.com> --- drivers/infiniband/hw/hfi1/file_ops.c | 2 +- drivers/infiniband/hw/hfi1/hfi.h | 2 +- drivers...

...10 PM, Jason Gunthorpe wrote: > > From: Jason Gunthorpe <jgg at mellanox.com> > > > > This converts one of the two users of mmu_notifiers to use the new API. > > The conversion is fairly straightforward, however the existing use of > > notifiers here seems to be racey. > > > > Cc: Mike Marciniszyn <mike.marciniszyn at intel.com> > > Cc: Dennis Dalessandro <dennis.dalessandro at intel.com> > > Signed-off-by: Jason Gunthorpe <jgg at mellanox.com> > > I tested v1, and replied to it [1]. I can re-test with this versi...

On 10/28/2019 4:10 PM, Jason Gunthorpe wrote: > From: Jason Gunthorpe <jgg at mellanox.com> > > This converts one of the two users of mmu_notifiers to use the new API. > The conversion is fairly straightforward, however the existing use of > notifiers here seems to be racey. > > Cc: Mike Marciniszyn <mike.marciniszyn at intel.com> > Cc: Dennis Dalessandro <dennis.dalessandro at intel.com> > Signed-off-by: Jason Gunthorpe <jgg at mellanox.com> I tested v1, and replied to it [1]. I can re-test with this version if you like as well. [1]...

http://bugzilla.mindrot.org/show_bug.cgi?id=220 ------- Additional Comments From djm at mindrot.org 2003-05-14 23:06 ------- Any followup on this, Ben? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

Greetings, We use NFSv4 on our cluster and perform distributed indexing (well, we used to on our previous system which used a simple touch() locking mechanism). I'm having a spot of bother getting Xapian to obtain a lock (hangs on fcntl64()). I've read http://trac.xapian.org/wiki/XapianOverNFS and other list posts, and noted that a lock daemon should be running to allow locks

...er::PrintHexArray()`` which ASan then catches but >> then the handler for the ASan detected nullptr derefence calls >> ``fuzzer::PrintHexArray()`` again and so we get stuck in a loop. Some >> how we are managing to break out of this loop but I'm guessing this >> probably racey which would probably also explain the very variable >> timings I've been seeing for test execution. >> >> >> [1] http://reviews.llvm.org/D20706 >> >> Dan. >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <h...

From: Jason Gunthorpe <jgg at mellanox.com> This converts one of the two users of mmu_notifiers to use the new API. The conversion is fairly straightforward, however the existing use of notifiers here seems to be racey. Tested-by: Dennis Dalessandro <dennis.dalessandro at intel.com> Signed-off-by: Jason Gunthorpe <jgg at mellanox.com> --- drivers/infiniband/hw/hfi1/file_ops.c | 2 +- drivers/infiniband/hw/hfi1/hfi.h | 2 +- drivers/infiniband/hw/hfi1/user_exp_rcv.c | 146 +++++++++--...

Probably needs a bit of cleanup, but seems like it is generally the right direction. One thing I've noticed is that the expect test randomly (but rarely) hangs :-( I guess something is racey but I don't know what at the moment. Rich.

From: Jason Gunthorpe <jgg at mellanox.com> 8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1, scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where they only use invalidate_range_start/end and immediately check the invalidating range against some driver data structure to tell if the driver is interested. Half of them use an interval_tree, the others

...qemu-system-ppc -cpu 7455 doesn't start Changed Bug submitter to 'J?rg Sommer <joerg at alea.gnuu.de>' from 'J??rg Sommer <joerg at alea.gnuu.de>' > submitter 660802 J?r?my Lal <kapouer at melix.org> Bug #660802 [nodejs] nodejs: test-cluster-kill-workers is racey Changed Bug submitter to 'J?r?my Lal <kapouer at melix.org>' from 'J??r??my Lal <kapouer at melix.org>' > submitter 660806 Stefan B?hler <lighttpd at stbuehler.de> Bug #660806 {Done: Nobuhiro Iwamatsu <iwamatsu at debian.org>} [libdispatch0] libdispatch0 u...

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

From: Jason Gunthorpe <jgg at mellanox.com> 8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1, scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where they only use invalidate_range_start/end and immediately check the invalidating range against some driver data structure to tell if the driver is interested. Half of them use an interval_tree, the others