search for: 04pm

On 11/25/2016 05:17 PM, Peter Zijlstra wrote: > On Fri, Nov 25, 2016 at 04:10:04PM +0000, Mark Rutland wrote: >> On Fri, Nov 25, 2016 at 04:21:39PM +0100, Dmitry Vyukov wrote: > >>> What are use cases for such primitive that won't be OK with "read once >>> _and_ atomically"? >> >> I have none to hand. > > Whatever trigg...

On 11/25/2016 05:17 PM, Peter Zijlstra wrote: > On Fri, Nov 25, 2016 at 04:10:04PM +0000, Mark Rutland wrote: >> On Fri, Nov 25, 2016 at 04:21:39PM +0100, Dmitry Vyukov wrote: > >>> What are use cases for such primitive that won't be OK with "read once >>> _and_ atomically"? >> >> I have none to hand. > > Whatever trigg...

On Fri, Jul 22, 2016 at 2:51 PM, The Doctor <doctor at doctor.nl2k.ab.ca> wrote: > On Fri, Jul 22, 2016 at 02:40:04PM +1000, Damien Miller wrote: [...] >> OpenSSH 5.3 is almost ready for release, so we would appreciate testing > ^ > Huh? Either a clone of Damien has been frozen Austin Powers style since 2009 and has only just been thawed out or maybe it was a typo. Tough to tell....

On Thu, Sep 12, 2002 at 10:54:04PM +0200, Miroslav Lichvar wrote: > I tried tagging using metaflac with some iso-8859-2 chars, but these > chars were replaced by '#' chars, something wrong is here. Ok, here is simple patch, it works for me, but I'm not familiar with this stuff. BTW, metaflac --list prints comment...

On Wed, Apr 27, 2016 at 04:37:04PM +0300, Michael S. Tsirkin wrote: > One correction: it's a feature of the device in the system. > There could be a mix of devices bypassing and not > bypassing the IOMMU. No, it really is not. A device can't chose to bypass the IOMMU. But the IOMMU can chose to let the device bypas...

On Wed, Apr 27, 2016 at 04:37:04PM +0300, Michael S. Tsirkin wrote: > One correction: it's a feature of the device in the system. > There could be a mix of devices bypassing and not > bypassing the IOMMU. No, it really is not. A device can't chose to bypass the IOMMU. But the IOMMU can chose to let the device bypas...

On Tue, Oct 22, 2019 at 12:11:04PM -0600, David G. Miller wrote: > "ip" should be used instead.? Likewise for using dnf instead of yum, > systemctl instead of service, firewallcmd instead of iptables, etc. > I wonder how many shell scripts there are "out there" that folks > have written or accumulated...

Vq log_base is the userspace address of bitmap which has nothing to do with IOTLB. So it needs to be validated unconditionally otherwise we may try use 0 as log_base which may lead to pin pages that will lead unexpected result (e.g trigger BUG_ON() in set_bit_to_user()). Fixes: 6b1e6cc7855b0 ("vhost: new device IOTLB API") Reported-by: syzbot+6304bf97ef436580fede at

Vq log_base is the userspace address of bitmap which has nothing to do with IOTLB. So it needs to be validated unconditionally otherwise we may try use 0 as log_base which may lead to pin pages that will lead unexpected result (e.g trigger BUG_ON() in set_bit_to_user()). Fixes: 6b1e6cc7855b0 ("vhost: new device IOTLB API") Reported-by: syzbot+6304bf97ef436580fede at

Hello, We are now facing a bug caused by the GVN pass, only part of the code was optimized. I have found that the problem is cause by an Limit in lib/Analysis/MemoryDependenceAnalysis.cpp 00055 static cl::opt<unsigned> BlockScanLimit( 00056 "memdep-block-scan-limit", cl::Hidden, cl::init(100), 00057 cl::desc("The number of instructions to scan in a block in

On Fri, Sep 20, 2013 at 04:39:04PM -0700, Rui Ueyama wrote: > I don't want to make Resolver to have a reference to input graph. The point > of this proposal is to separate input graph handling from Resolver and > instead making Linker Context to do that task. That was the part of the original proposal I didn't agre...

On Wed, Feb 24, 2016 at 01:52:04PM +0100, Pino Toscano wrote: > It eases the debugging, instead of getting just the name of the struct > returned. The series is fine, so ACK. Definitely improves the trace output :-) A few things that would be good though: - Export the functions through the public API. We already have...

On Mon, 22 Jul, at 12:07:34PM, Matt Fleming wrote: > On Thu, 18 Jul, at 01:22:04PM, Adrian Irimia wrote: > > Hi, > > ? > > ? I have a bootable usb with syslinux 5.10 on wich the following?code is working ok. > > ??? LABEL - > > ?? MENU LABEL GRUB LEGACY > > ?? MENU INDENT 1 > > ???? COM32 chain.c32 > > ???? APPEND boot fs grub=/boot...

On Thu, Jun 13, 2019 at 06:23:04PM -0700, John Hubbard wrote: > On 6/13/19 5:43 PM, Ira Weiny wrote: > > On Thu, Jun 13, 2019 at 07:58:29PM +0000, Jason Gunthorpe wrote: > >> On Thu, Jun 13, 2019 at 12:53:02PM -0700, Ralph Campbell wrote: > >>> > ... > >> Hum, so the only thing this config d...

Hi, ? ? I have a bootable usb with syslinux 5.10 on wich the following?code is working ok. ??? LABEL - ?? MENU LABEL GRUB LEGACY ?? MENU INDENT 1 ???? COM32 chain.c32 ???? APPEND boot fs grub=/boot/grub-legacy/stage2 grubcfg=/boot/grub-legacy/grub-legacy.cfg nohand nosect ? ?After upgrading to syslinux 6.01 (using bios) I receive the following errors when selecting that menu option : ? ? ERR:

Hi everybody, I am using btrfs as my main fs for some time now, but I am experiencing severe performance drawbacks. I can''t qualify the circumstances, but sometimes during disc access the whole system freezes for some time. Maybe somebody could suggest some general things I could try to search for the problem? Thanks in advance, Florian --- Some background information: $ mount |

On 2018?09?28? 01:04, Michael S. Tsirkin wrote: > On Thu, Sep 27, 2018 at 08:22:04PM +0800, Jason Wang wrote: >> The access of vsock is not protected by vhost_vsock_lock. This may >> lead to use after free since vhost_vsock_dev_release() may free the >> pointer at the same time. >> >> Fix this by holding the lock during the access. >> >> Re...

On 2018?09?28? 01:04, Michael S. Tsirkin wrote: > On Thu, Sep 27, 2018 at 08:22:04PM +0800, Jason Wang wrote: >> The access of vsock is not protected by vhost_vsock_lock. This may >> lead to use after free since vhost_vsock_dev_release() may free the >> pointer at the same time. >> >> Fix this by holding the lock during the access. >> >> Re...

...the VM is "running," it will occasionally just stop when I am transitioning into the VM from elsewhere. I verified this using the CentOS system clock - last night it stopped at 23:01 and still read 23:01 when my cell phone, which is usually dead on in sync with the system clock, read 11:04pm. I cut back on the amount of memory allowed to the Windows VM (768MB, down from 1GB) and that seemed to help a little, but I have 2GB and I'm thinking that this should not be a problem. Any input would be helpful. Thanks. mhr P.S.: Now I'm thinking that my earlier remark about applicat...

On Fri, Nov 06, 2015 at 04:17:04PM -0800, Hans Wennborg via llvm-dev wrote: > On Fri, Nov 6, 2015 at 9:56 AM, Chris Bieneman via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > Hi LLVMDev, > > > > Since my last update we???ve landed patches for these issues: > > * Bug 14200 - -fno-rtti not in c...