search for: 0ul

First off, thanks -- this is a pretty great library and it feels like I'm learning a lot. I'm getting some more experience with libfuzzer and finding that I have a couple of questions: - How does libfuzzer decide to write a new test file? What distinguishes this one from all the other cases for which new test inputs were not written? Must be something about the path taken through the

...0001290) at /home/brian/tmp/testing/llvm_src/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_linux.cc:471 #2 0x0000000000447899 in GenericScopedLock (mu=mu at entry=0x640000001290, this=<synthetic pointer>) #3 __sanitizer::SizeClassAllocator64<105553116266496ul, 4398046511104ul, 0ul, __sanitizer::SizeClassMap<17ul, 128ul, 16ul>, __asan::AsanMapUnmapCallback>::PopulateFreeList ( #4 0x0000000000447ff8 in __sanitizer::SizeClassAllocator64<105553116266496ul, 4398046511104ul, 0ul, __sanitizer::SizeClassMap<17ul, 128ul, 16ul>, __asan::AsanMapUnmapCallback>::All...

...-r b58bcd6551e2 xen/arch/ia64/xen/domain.c --- a/xen/arch/ia64/xen/domain.c Fri Dec 01 16:21:46 2006 +0000 +++ b/xen/arch/ia64/xen/domain.c Fri Dec 01 16:22:41 2006 +0000 @@ -911,7 +911,7 @@ void alloc_dom0(void) */ static void physdev_init_dom0(struct domain *d) { - if (iomem_permit_access(d, 0UL, ~0UL)) + if (iomem_permit_access(d, 0UL, ~0UL, IOMEM_ACCESS_READWRITE)) BUG(); if (irqs_permit_access(d, 0, NR_IRQS-1)) BUG(); diff -r b58bcd6551e2 xen/arch/ia64/xen/mm.c --- a/xen/arch/ia64/xen/mm.c Fri Dec 01 16:21:46 2006 +0000 +++ b/xen/arch/ia64/xen/mm.c Fri Dec 01 16:22:41 200...

...work on addresses. */ + if (vaddr >= KERNEL_START + && vaddr < (KERNEL_START + KERNEL_TR_PAGE_SIZE)) + return vaddr - kernel_virtual_offset; + + /* In kernel area -- virtually mapped. */ + pgd = pgd_offset_k(vaddr); + if (pgd_none(*pgd) || pgd_bad(*pgd)) + return ~0UL; + + pud = pud_offset(pgd, vaddr); + if (pud_none(*pud) || pud_bad(*pud)) + return ~0UL; + + pmd = pmd_offset(pud, vaddr); + if (pmd_none(*pmd) || pmd_bad(*pmd)) + return ~0UL; + + ptep = pte_offset_kernel(pmd, vaddr); + if (!ptep) + return ~0UL; + + return (pte_val(*ptep) & _PFN_M...

...work on addresses. */ + if (vaddr >= KERNEL_START + && vaddr < (KERNEL_START + KERNEL_TR_PAGE_SIZE)) + return vaddr - kernel_virtual_offset; + + /* In kernel area -- virtually mapped. */ + pgd = pgd_offset_k(vaddr); + if (pgd_none(*pgd) || pgd_bad(*pgd)) + return ~0UL; + + pud = pud_offset(pgd, vaddr); + if (pud_none(*pud) || pud_bad(*pud)) + return ~0UL; + + pmd = pmd_offset(pud, vaddr); + if (pmd_none(*pmd) || pmd_bad(*pmd)) + return ~0UL; + + ptep = pte_offset_kernel(pmd, vaddr); + if (!ptep) + return ~0UL; + + return (pte_val(*ptep) & _PFN_M...

...index d984141..06257dd 100644 --- a/drivers/net/xen-netback/interface.c +++ b/drivers/net/xen-netback/interface.c @@ -273,6 +273,7 @@ struct xenvif *xenvif_alloc(struct device *parent, domid_t domid, INIT_LIST_HEAD(&vif->notify_list); vif->credit_bytes = vif->remaining_credit = ~0UL; + vif->credit_packets = vif->remaining_packets = ~0UL; vif->credit_usec = 0UL; init_timer(&vif->credit_timeout); /* Initialize ''expires'' now: it''s used to track the credit window. */ diff --git a/drivers/net/xen-netback/netback.c b/drivers/net/xen-...

...ybe this could be due to some interaction > with your blockdevice in pagecache > > I don't know if you already have a fix in your tree. Maybe sct can > provide you with more info You need to upgrade glibc to something recent like 2.2.1, so that the ulimit will be correctly set to ~0UL. We could also fix this problem in the kernel but even if we do you will still run into troubles with LFS with the mounted filesystems. Or maybe you run really play with the blkdev with file limits not set to unlimited? I think it's insane to set file limits for root during boot, the only prob...

...); xfree(dom_vmce(d)); dom_vmce(d) = NULL; } @@ -93,9 +82,8 @@ switch ( msr & (MSR_IA32_MC0_CTL | 3) ) { case MSR_IA32_MC0_CTL: - if ( bank < nr_mce_banks ) - *val = vmce->mci_ctl[bank] & - (h_mci_ctrl ? h_mci_ctrl[bank] : ~0UL); + /* stick all 1''s to MCi_CTL */ + *val = ~0UL; mce_printk(MCE_VERBOSE, "MCE: rdmsr MC%u_CTL 0x%"PRIx64"\n", bank, *val); break; @@ -220,8 +208,10 @@ switch ( msr & (MSR_IA32_MC0_CTL | 3) ) { case...

...ct nouveau_svmm **psvmm) > { > struct nouveau_svmm *svmm = *psvmm; > + struct mmu_interval_notifier *mni; > + > if (svmm) { > mutex_lock(&svmm->mutex); > + while (true) { > + mni = mmu_interval_notifier_find(svmm->mm, > + &nouveau_svm_mni_ops, 0UL, ~0UL); > + if (!mni) > + break; > + mmu_interval_notifier_put(mni); Oh, now I really don't like the name 'put'. It looks like mni is refcounted here, and it isn't. put should be called 'remove_deferred' And then you also need a way to barrier this scheme o...

...ybe this could be due to some interaction > with your blockdevice in pagecache > > I don't know if you already have a fix in your tree. Maybe sct can > provide you with more info You need to upgrade glibc to something recent like 2.2.1, so that the ulimit will be correctly set to ~0UL. We could also fix this problem in the kernel but even if we do you will still run into troubles with LFS with the mounted filesystems. Or maybe you run really play with the blkdev with file limits not set to unlimited? I think it's insane to set file limits for root during boot, the only prob...

...t;> struct nouveau_svmm *svmm = *psvmm; >> + struct mmu_interval_notifier *mni; >> + >> if (svmm) { >> mutex_lock(&svmm->mutex); >> + while (true) { >> + mni = mmu_interval_notifier_find(svmm->mm, >> + &nouveau_svm_mni_ops, 0UL, ~0UL); >> + if (!mni) >> + break; >> + mmu_interval_notifier_put(mni); > > Oh, now I really don't like the name 'put'. It looks like mni is > refcounted here, and it isn't. put should be called 'remove_deferred' OK. > And then you als...

...is is necessary, because 386 hardware has concept of busy TSS or some similar stupidity. */ + + load_TR(cpu); /* This does ltr */ + __asm__ __volatile__ ( "lldt %%ax" : : "a" (0) );/* This does lldt */ + + /* + * Now maybe reset the debug registers + */ + set_debugreg(0UL, 0); + set_debugreg(0UL, 1); + set_debugreg(0UL, 2); + set_debugreg(0UL, 3); + /* no 4 and 5 */ + set_debugreg(0UL, 6); + set_debugreg(0UL, 7); +} +#endif void __restore_processor_state(struct saved_context *ctxt) { @@ -106,15 +216,19 @@ void __restore_processor_state(struct sa * segment reg...

1: correct LDT checks 2: add address validity check to guest_map_l1e() 3: use {rd,wr}{fs,gs}base when available 4: check for canonical address before doing page walks Signed-off-by: Jan Beulich <jbeulich@suse.com>

...h the first function *argument* parameter and not the return parameter. The index argument to LLVMGetParams() is actually incremented by one when it's mapped to the index used for the Function::AttributeList member. There are separate functions for the function attributes, which are at index ~0UL, but no similar functions for handling the function return parameter attribute at index zero. Is this intentional? What is the correct way to get and set a function return parameter attribute with C-language binding to the LLVM core? — j h woodyatt <jhw at conjury.org> http://jhw.dreamwid...

I think I have bumped into the small file error, or I''m doing something stupid. The files are short audio effects for a game (embedded in our own data format). Sample info: Vorbis packets: 1 (4 kb) Samples: 28672 Samplerate: 22 kHz Channels: 2 This is what I''m doing when I want to get a number of bytes from the stream: The problem is that ov_pcm_tell always returns 0. And so

...unsigned long size) +{ + const unsigned long *p = addr; + unsigned long result = 0; + unsigned long tmp; + + while (size & ~(BITS_PER_LONG-1)) { + if ((tmp = *(p++))) + goto found; + result += BITS_PER_LONG; + size -= BITS_PER_LONG; + } + if (!size) + return result; + + tmp = (*p) & (~0UL >> (BITS_PER_LONG - size)); + if (tmp == 0UL) /* Are any bits set? */ + return result + size; /* Nope. */ +found: + return result + __ffs(tmp); +} + +/* + * Find the next set bit in a memory region. + */ +static inline unsigned long +find_next_bit(const unsigned long *addr, unsigned long si...

...notifier, -}; - void nouveau_svmm_fini(struct nouveau_svmm **psvmm) { struct nouveau_svmm *svmm = *psvmm; + struct mmu_interval_notifier *mni; + if (svmm) { mutex_lock(&svmm->mutex); + while (true) { + mni = mmu_interval_notifier_find(svmm->mm, + &nouveau_svm_mni_ops, 0UL, ~0UL); + if (!mni) + break; + mmu_interval_notifier_put(mni); + } svmm->vmm = NULL; mutex_unlock(&svmm->mutex); - mmu_notifier_put(&svmm->notifier); + mmdrop(svmm->mm); + kfree(svmm); *psvmm = NULL; } } @@ -343,11 +319,12 @@ nouveau_svmm_init(struct drm_d...

...erface.c b/drivers/net/xen-netback/interface.c index 01bb854..459935a 100644 --- a/drivers/net/xen-netback/interface.c +++ b/drivers/net/xen-netback/interface.c @@ -312,8 +312,7 @@ struct xenvif *xenvif_alloc(struct device *parent, domid_t domid, vif->credit_bytes = vif->remaining_credit = ~0UL; vif->credit_usec = 0UL; init_timer(&vif->credit_timeout); - /* Initialize ''expires'' now: it''s used to track the credit window. */ - vif->credit_timeout.expires = jiffies; + vif->credit_window_start = get_jiffies_64(); dev->netdev_ops = &xe...

Three of the patches could be squashed in one, but it makes more sense to review them as three. These patches fix the case of an PVHVM guest not being able to resume propely b/c of hitting: 142 BUG_ON(info->type != IRQT_UNBOUND && info->type != type); (in events.c) and also adds a WARN to catch situations like these. The reason for this is that the Xen python toolstack

...h the first function *argument* parameter and not the return parameter. The index argument to LLVMGetParams() is actually incremented by one when it's mapped to the index used for the Function::AttributeList member. There are separate functions for the function attributes, which are at index ~0UL, but no similar functions for handling the function return parameter attribute at index zero. > > Is this intentional? What is the correct way to get and set a function return parameter attribute with C-language binding to the LLVM core? I'm sorry to be a pest about this question, but...