[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2024-06-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|RESOLVED|CLOSED --

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2024-06-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2024-04-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 --- Comment #17 from Erhard F. (erhar...@mailbox.org) --- Just noticed the issue is still there in v6.9-rc4. Does some side effects prevented the patch to get upstream or was it overlooked? ;) [..] Page orders: linear mapping = 12, virtual = 12,

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2023-10-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 --- Comment #16 from Erhard F. (erhar...@mailbox.org) --- Your newest patch fixes the issue. Thanks! -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2023-10-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 --- Comment #15 from Michael Ellerman (mich...@ellerman.id.au) --- Yeah, facepalm. Calling kmemleak_no_scan() later doesn't help, because it's the early allocation that is ignored, leading to the warning. So we can just drop the call to

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2023-10-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 --- Comment #14 from Erhard F. (erhar...@mailbox.org) --- Thanks for having a look at the issue! Applied your patch on top of v6.5.6 but it didn't work out. Now I get: [...] drmem: No dynamic reconfiguration memory found ata5.00: ATAPI:

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2023-10-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 Michael Ellerman (mich...@ellerman.id.au) changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2023-10-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 --- Comment #12 from Erhard F. (erhar...@mailbox.org) --- Created attachment 305198 --> https://bugzilla.kernel.org/attachment.cgi?id=305198=edit kernel .config (5.18, PowerMac G5 11,2) -- You may reply to this email to add a comment. You

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2023-10-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 --- Comment #11 from Erhard F. (erhar...@mailbox.org) --- Created attachment 305197 --> https://bugzilla.kernel.org/attachment.cgi?id=305197=edit bisect.log -- You may reply to this email to add a comment. You are receiving this mail

[Bug 216156] [bisected] kmemleak: Not scanning unknown object at 0xc00000007f000000

2023-10-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216156 Erhard F. (erhar...@mailbox.org) changed: What|Removed |Added Summary|kmemleak: Not scanning |[bisected] kmemleak: