> -----Original Message----- > From: Borislav Petkov [mailto:bp@xxxxxxxxx] > Sent: Wednesday, November 04, 2015 4:00 AM > > On Mon, Nov 02, 2015 at 06:47:29AM +0000, Kweh, Hock Leong wrote: > > By looking at your dmesg log, the above print out message seem that > > someone has called the flush() after the write(2). In my environment, > flush() > > only being called in 2 places which are before write(2) and during close(2). > > The dmesg log seems that your environment is running write(2) and flush() > in > > different threads and are parallel. Could you help me to double confirm this > and it > > would be good if you could told me when the flush() is exactly being called > in > > your environment. The info really help me on debugging. > > I don't know what you mean: I simply do > > cat /bin/ls > /dev/efi_capsule_loader > > as root in an SMP kvm guest. And it explodes. Nothing special, just this > one command. > > I guess you could try to reproduce it, here's how I start it: > > qemu-system-x86_64 > -enable-kvm > -gdb tcp::1234 > -cpu Opteron_G5 > -m 2048 > -hda /home/boris/kvm/debian/sid-x86_64.img > -hdb /home/boris/kvm/swap.img > -boot menu=off,order=c > -localtime > -net nic,model=rtl8139 > -net user,hostfwd=tcp::1235-:22 > -usbdevice tablet > -kernel /home/boris/kernel/linux-2.6/arch/x86/boot/bzImage > -append "root=/dev/sda1 resume=/dev/sdb1 debug ignore_loglevel > log_buf_len=16M earlyprintk=ttyS0,115200 console=ttyS0,115200 > console=tty0" > -monitor pty > -virtfs local,path=/tmp,mount_tag=tmp,security_model=none > -serial file:/home/boris/kvm/test-x86_64-1235.log > -snapshot > -smp 8 > > HTH. > > -- > Regards/Gruss, > Boris. Hi Borislav, Finally able to free up 25GB space to setup a QEMU VM with Debian v8.2.0 system and look into this issue. Located the NULL pointer happened at code line: status = efi.query_capsule_caps(&capsule, 1, &max_size, reset); which is inside function efi_capsule_supported(). This function call is initialized by EFI Firmware run-time service table. So, I believe the QEMU do not emulate the EFI Firmware run-time service API calls. This is why when come to this line it hit the NULL pointer issue. So, my conclusion is that this module is not able to be tested on QEMU environment. Thanks & Regards, Wilson ��.n��������+%������w��{.n�����{����* jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
