** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1878641
Title:
Abort() in mch_update_pciexbar
Status in QEMU:
Fix Released
net/bugs/1878641
Title:
Abort() in mch_update_pciexbar
Status in QEMU:
Fix Committed
Bug description:
Hello,
I found an input which triggers an abort() in mch_update_pciexbar:
#0 0x7686d761 in __GI_raise (sig=sig@entry=0x6) at
../sysdeps/unix/sysv/linux/raise.c:50
On 5/26/21 1:06 PM, Thomas Huth wrote:
> Confirmed, this is not fixed yet. Philippe, what happened to your patch?
I was waiting someone suggest me how to propagate error from
PCIConfigWriteFunc. Probably not very important.
ort() in mch_update_pciexbar
Status in QEMU:
Confirmed
Bug description:
Hello,
I found an input which triggers an abort() in mch_update_pciexbar:
#0 0x7686d761 in __GI_raise (sig=sig@entry=0x6) at
../sysdeps/unix/sysv/linux/raise.c:50
#1 0x7685755b in __GI_abort ()
Proposed fix:
https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg05612.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1878641
Title:
Abort() in mch_update_pciexbar
Status in QEMU:
New
Public bug reported:
Hello,
I found an input which triggers an abort() in mch_update_pciexbar:
#0 0x7686d761 in __GI_raise (sig=sig@entry=0x6) at
../sysdeps/unix/sysv/linux/raise.c:50
#1 0x7685755b in __GI_abort () at abort.c:79
#2 0x5705c7ae in mch_update_pciexbar
On 200511 0910, Philippe Mathieu-Daudé wrote:
> On 5/11/20 8:19 AM, Philippe Mathieu-Daudé wrote:
> > On 5/11/20 6:59 AM, Alexander Bulekov wrote:
> > > Hello,
> > > While fuzzing, I found an input that triggers an assertion failure in
> > > mch_update_pciexbar:
> > >
> > > #6 0x7f38d387c55a in ab
On 5/11/20 9:39 AM, Michael S. Tsirkin wrote:
On Mon, May 11, 2020 at 09:10:48AM +0200, Philippe Mathieu-Daudé wrote:
On 5/11/20 8:19 AM, Philippe Mathieu-Daudé wrote:
On 5/11/20 6:59 AM, Alexander Bulekov wrote:
Hello,
While fuzzing, I found an input that triggers an assertion failure i
On Mon, May 11, 2020 at 09:10:48AM +0200, Philippe Mathieu-Daudé wrote:
> On 5/11/20 8:19 AM, Philippe Mathieu-Daudé wrote:
> > On 5/11/20 6:59 AM, Alexander Bulekov wrote:
> > > Hello,
> > > While fuzzing, I found an input that triggers an assertion failure in
> > > mch_update_pciexbar:
> > >
>
On 5/11/20 8:19 AM, Philippe Mathieu-Daudé wrote:
On 5/11/20 6:59 AM, Alexander Bulekov wrote:
Hello,
While fuzzing, I found an input that triggers an assertion failure in
mch_update_pciexbar:
#6 0x7f38d387c55a in abort
/build/glibc-GwnBeO/glibc-2.30/stdlib/abort.c:79:7
#7 0x55c27e94ffd0 in m
On 5/11/20 6:59 AM, Alexander Bulekov wrote:
Hello,
While fuzzing, I found an input that triggers an assertion failure in
mch_update_pciexbar:
#6 0x7f38d387c55a in abort /build/glibc-GwnBeO/glibc-2.30/stdlib/abort.c:79:7
#7 0x55c27e94ffd0 in mch_update_pciexbar hw/pci-host/q35.c:331:9
#8 0x55c27
Hello,
While fuzzing, I found an input that triggers an assertion failure in
mch_update_pciexbar:
#6 0x7f38d387c55a in abort /build/glibc-GwnBeO/glibc-2.30/stdlib/abort.c:79:7
#7 0x55c27e94ffd0 in mch_update_pciexbar hw/pci-host/q35.c:331:9
#8 0x55c27e94db38 in mch_write_config hw/pci-host/q35.c:4
12 matches
Mail list logo
