similar to: Device release NULL pointer dereference

Hi there, I just found a segfaulting tapdisk2 process which led into a kernel oops. [1527071.169682] tapdisk2[26548]: segfault at 7fffd324cfe8 ip 000000000040837f sp 00007fffd324cff0 error 6 in tapdisk2[400000+38000] [1527071.220104] BUG: unable to handle kernel NULL pointer dereference at 0000000000000048 [1527071.220170] IP: [<ffffffff810ce73c>] apply_to_page_range+0x47/0x2f3

Hello, I'm looking at compiling some pieces of the standard library with llvm but I'm running into problems with some functions being renamed by dragonegg. For example, when I compile the acos implementation with plain gcc I get: $ nm acos.o 0000000000000000 r .LC1 0000000000000048 r .LC10 0000000000000050 r .LC11 0000000000000058 r .LC12 0000000000000060 r .LC13 0000000000000068 r .LC14

Hi Gregory, > I'm looking at compiling some pieces of the standard library with llvm but I'm > running into problems with some functions being renamed by dragonegg. For > example, when I compile the acos implementation with plain gcc I get: > > $ nm acos.o > 0000000000000000 r .LC1 > 0000000000000048 r .LC10 > 0000000000000050 r .LC11 > 0000000000000058 r .LC12

with your patches I get this in dmesg when removing nouveau: [ 202.510730] ------------[ cut here ]------------ [ 202.510731] sysfs group 'power' not found for kobject 'nv_backlight' [ 202.510736] WARNING: CPU: 0 PID: 8156 at fs/sysfs/group.c:235 sysfs_remove_group+0x71/0x80 [ 202.510736] Modules linked in: nouveau(-) r8168(O) ttm zram [last unloaded: nouveau] [ 202.510740]

The MS x64 ABI calling convention (http://msdn.microsoft.com/en-us/library/ms235286(VS.80).aspx) says: Any argument that doesn’t fit in 8 bytes, or is not 1, 2, 4, or 8 bytes, must be passed by reference. Clang isn't doing that for us when passing our triple, x86_64-pc-win32-macho. Here's a simple example program: struct Guid { unsigned int Data1; unsigned

Carl, See clang/lib/CodeGen/TargetInfo.cpp. // FIXME: mingw64-gcc emits 128-bit struct as i128 if (Size <= 128 && (Size & (Size - 1)) == 0) return ABIArgInfo::getDirect(llvm::IntegerType::get(getVMContext(), Size)); It was my workaround, sorry. Please check to tweak the clause (128 to 64) and lemme

Hi Duncan, Ah, non-unicode email... In the llvm output there should be a "1" character, i.e. (char) 0x01, prepended to acos and __GI_acos. I'm unable to get it on smaller things, but it happens when I try to compile uClibc with llvm. I've attached the .o and the .bc for comparison. The text file is the result after preprocessing (to avoid having to download a bunch of stuff).

And some more information ... Am 2014-10-13 12:04, schrieb Jonas Meurer: > Am 2014-08-19 12:26, schrieb Jonas Meurer: >> I encounter kernel crashes on an up-to-date Debian/Wheezy Xen domU >> with the >> stock kernel. The dom0 runs the same linux kernel and >> xen/4.1.4-3+deb7u1. > > the bug is still reproducible with the latest kernel and Xen packages >

Hey again, Am 2014-08-19 12:26, schrieb Jonas Meurer: > I encounter kernel crashes on an up-to-date Debian/Wheezy Xen domU with > the > stock kernel. The dom0 runs the same linux kernel and > xen/4.1.4-3+deb7u1. the bug is still reproducible with the latest kernel and Xen packages from Debian Wheezy. Unfortunately it seems like a corner case, somehow related to the hardware

nevermind, I just hit it today. Will test your patches On Tue, Jul 17, 2018 at 12:46 PM, Karol Herbst <kherbst at redhat.com> wrote: > does this also happen with the newest kernel? I was kind of under the > impression we already fixed such issues. > > On Thu, Jul 5, 2018 at 9:09 PM, Jeffery Miller <jmiller at neverware.com> wrote: >> If have a couple patches I found

Hi Pavel, thank you for you response. objdump -T showed that there are no symbols defined in liblldb.so. After few compilations I found that problem is with linking with LLD (-DLLVM_ENABLE_LLD=ON) without the directive everything is ok. Hana ============= $ objdump -T lib64/liblldb.so lib64/liblldb.so: file format elf64-x86-64 DYNAMIC SYMBOL TABLE: 0000000000000000 w D *UND*

Hello, I update my building scripts to build LLVM 4.0 RC1 (with clang, lldb, libc++, libc++abi, lld) on CentOS 6 and I got a lot of undefined symbols during linking LLDB. I'm using clang-3.9 and this configuration: -DLLVM_TARGETS_TO_BUILD="X86" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: normal Hello, I was running Xen for a few years and after a PSU failure I never got the system working stable again. I suspected damage to the board so I replaced everything in the system piece by piece but Xen enabled kernel always crashes even with only Dom0 running when moderate amount of IO happens on the box. kvm seems