search for: misattribut

...ighten us. > > @Andrew, any guidance here? Should we really add all memory to the > firmware memmap, even if this contradicts with the existing > documentation? (especially, if the actual firmware memmap will *not* > contain that memory after a reboot) For some reason that patch is misattributed - it was authored by Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in a decade. I looked through the email discussion from that time and I'm not seeing anything useful. But I wasn't able to locate Dave Hansen's review comments.

...ighten us. > > @Andrew, any guidance here? Should we really add all memory to the > firmware memmap, even if this contradicts with the existing > documentation? (especially, if the actual firmware memmap will *not* > contain that memory after a reboot) For some reason that patch is misattributed - it was authored by Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in a decade. I looked through the email discussion from that time and I'm not seeing anything useful. But I wasn't able to locate Dave Hansen's review comments.

...re? Should we really add all memory to the > >> firmware memmap, even if this contradicts with the existing > >> documentation? (especially, if the actual firmware memmap will *not* > >> contain that memory after a reboot) > > > > For some reason that patch is misattributed - it was authored by > > Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in > > a decade. I looked through the email discussion from that time and I'm > > not seeing anything useful. But I wasn't able to locate Dave Hansen's > &g...

...re? Should we really add all memory to the > >> firmware memmap, even if this contradicts with the existing > >> documentation? (especially, if the actual firmware memmap will *not* > >> contain that memory after a reboot) > > > > For some reason that patch is misattributed - it was authored by > > Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in > > a decade. I looked through the email discussion from that time and I'm > > not seeing anything useful. But I wasn't able to locate Dave Hansen's > &g...

...he > >>>> firmware memmap, even if this contradicts with the existing > >>>> documentation? (especially, if the actual firmware memmap will *not* > >>>> contain that memory after a reboot) > >>> > >>> For some reason that patch is misattributed - it was authored by > >>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in > >>> a decade. I looked through the email discussion from that time and I'm > >>> not seeing anything useful. But I wasn't able to locate D...

...he > >>>> firmware memmap, even if this contradicts with the existing > >>>> documentation? (especially, if the actual firmware memmap will *not* > >>>> contain that memory after a reboot) > >>> > >>> For some reason that patch is misattributed - it was authored by > >>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in > >>> a decade. I looked through the email discussion from that time and I'm > >>> not seeing anything useful. But I wasn't able to locate D...

...mware memmap, even if this contradicts with the existing >>>>>>> documentation? (especially, if the actual firmware memmap will *not* >>>>>>> contain that memory after a reboot) >>>>>> >>>>>> For some reason that patch is misattributed - it was authored by >>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>>>>> a decade. I looked through the email discussion from that time and I'm >>>>>> not seeing anything useful. But I wasn...

...mware memmap, even if this contradicts with the existing >>>>>>> documentation? (especially, if the actual firmware memmap will *not* >>>>>>> contain that memory after a reboot) >>>>>> >>>>>> For some reason that patch is misattributed - it was authored by >>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>>>>> a decade. I looked through the email discussion from that time and I'm >>>>>> not seeing anything useful. But I wasn...

...redhat.com> > > If you believe a bug is no longer valid, please close the syzbot report by > sending a '#syz fix', '#syz dup', or '#syz invalid' command in reply to the > original thread, as explained at https://goo.gl/tpsmEJ#status > > If you believe I misattributed a bug to the vhost subsystem, please let me know, > and if possible forward the report to the correct people or mailing list. > > Here are the bugs: > > -------------------------------------------------------------------------------- > Title: KASAN: use-after-free W...

...> If you believe a bug is no longer valid, please close the syzbot report by > > sending a '#syz fix', '#syz dup', or '#syz invalid' command in reply to the > > original thread, as explained at https://goo.gl/tpsmEJ#status > > > > If you believe I misattributed a bug to the vhost subsystem, please let me know, > > and if possible forward the report to the correct people or mailing list. > > > > Here are the bugs: > > > > -------------------------------------------------------------------------------- > > Title:...

...@Andrew, any guidance here? Should we really add all memory to the >> firmware memmap, even if this contradicts with the existing >> documentation? (especially, if the actual firmware memmap will *not* >> contain that memory after a reboot) > > For some reason that patch is misattributed - it was authored by > Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in > a decade. I looked through the email discussion from that time and I'm > not seeing anything useful. But I wasn't able to locate Dave Hansen's > review comments....

...s constant input argument because I want to label it with the correct DebugLoc. Currently, the InlineAsm MachineInstr itself has the correct DebugLoc, but all the MOVs to registers that are spawned for any (e.g. integer) constant input arguments do not have DebugLoc associated with them, leading to misattribution of some source lines. I can't seem to find the specific place where those instructions are generated from the IR and I'd appreciate any hints. I realize this issue might be specific to my custom backend - which is similar to the x86 backend - but finding the place where this is done in e...

...adicts with the existing >>>>>>>>> documentation? (especially, if the actual firmware memmap will *not* >>>>>>>>> contain that memory after a reboot) >>>>>>>> >>>>>>>> For some reason that patch is misattributed - it was authored by >>>>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>>>>>>> a decade. I looked through the email discussion from that time and I'm >>>>>>>> not seeing anythi...

...adicts with the existing >>>>>>>>> documentation? (especially, if the actual firmware memmap will *not* >>>>>>>>> contain that memory after a reboot) >>>>>>>> >>>>>>>> For some reason that patch is misattributed - it was authored by >>>>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>>>>>>> a decade. I looked through the email discussion from that time and I'm >>>>>>>> not seeing anythi...

...the last week. > > If you believe a bug is no longer valid, please close the syzbot report by > sending a '#syz fix', '#syz dup', or '#syz invalid' command in reply to the > original thread, as explained at https://goo.gl/tpsmEJ#status > > If you believe I misattributed a bug to the vhost subsystem, please let me know, > and if possible forward the report to the correct people or mailing list. > > Here are the bugs: > > -------------------------------------------------------------------------------- > Title: memory leak in vhost_ne...

...eally add all memory to the >>>> firmware memmap, even if this contradicts with the existing >>>> documentation? (especially, if the actual firmware memmap will *not* >>>> contain that memory after a reboot) >>> >>> For some reason that patch is misattributed - it was authored by >>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>> a decade. I looked through the email discussion from that time and I'm >>> not seeing anything useful. But I wasn't able to locate Dave Hansen'...

...>>> firmware memmap, even if this contradicts with the existing >>>>>> documentation? (especially, if the actual firmware memmap will *not* >>>>>> contain that memory after a reboot) >>>>> >>>>> For some reason that patch is misattributed - it was authored by >>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>>>> a decade. I looked through the email discussion from that time and I'm >>>>> not seeing anything useful. But I wasn't able to...

...;>>>>>>>>> documentation? (especially, if the actual firmware memmap will *not* >>>>>>>>>>> contain that memory after a reboot) >>>>>>>>>> >>>>>>>>>> For some reason that patch is misattributed - it was authored by >>>>>>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>>>>>>>>> a decade. I looked through the email discussion from that time and I'm >>>>>>>>&g...

...;>>>>>>>>> documentation? (especially, if the actual firmware memmap will *not* >>>>>>>>>>> contain that memory after a reboot) >>>>>>>>>> >>>>>>>>>> For some reason that patch is misattributed - it was authored by >>>>>>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in >>>>>>>>>> a decade. I looked through the email discussion from that time and I'm >>>>>>>>&g...

...f this contradicts with the existing > >>>>>>> documentation? (especially, if the actual firmware memmap will *not* > >>>>>>> contain that memory after a reboot) > >>>>>> > >>>>>> For some reason that patch is misattributed - it was authored by > >>>>>> Shaohui Zheng <shaohui.zheng at intel.com>, who hasn't been heard from in > >>>>>> a decade. I looked through the email discussion from that time and I'm > >>>>>> not seeing anything useful...