{"push_id":1179550067,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"15994b89b9cbbd5f95f78cb9cdb927f406dff511","before":"db552975315fec06a957c937803935d8fbddfd2d","commits":[{"sha":"15994b89b9cbbd5f95f78cb9cdb927f406dff511","author":{"name":"Dave Anderson","email":"a54029788db59871856f36aa6c9fcef2b8a1f47d@redhat.com"},"message":"Fix to recognize a kernel thread that has user space virtual memory\nattached to it.  While kernel threads typically do not have an\nmm_struct referencing a user-space virtual address space, they can\neither temporarily reference one for a user-space copy operation, or\nin the case of KVM \"vhost\" kernel threads, keep a reference to the\nuser space of the \"quem-kvm\" task that created them.  Without the\npatch, they will be mistaken for user tasks; the \"bt\" command will\ndisplay an invalid kernel-entry exception frame that indicates\n\"[exception RIP: unknown or invalid address]\", the \"ps\" command\nwill not enclose the command name with brackets, and the \"ps -[uk]\"\nand \"foreach [user|kernel]\" options will show the kernel thread as\na user task.\n(anderson@redhat.com)","distinct":true,"url":"https://api.github.com/repos/crash-utility/crash/commits/15994b89b9cbbd5f95f78cb9cdb927f406dff511"}]}
{"actor":{"display_login":"crash-utility"}}