https://bugzilla.kernel.org/show_bug.cgi?id=194579 --- Comment #11 from Christian König (deathsimple@xxxxxxxxxxx) --- (In reply to PaX Team from comment #9) > would the following workaround do the job of not triggering the overflow and > not causing any other logic bugs for our purposes: Not really. The issue is that the offset handling should actually be transparent to TTM. So mem.start can have any value here which might as well overflow during the assignment. So even with Nicolais suggestion of using LONG_MAX I would NAK the patch. The only clean solution I can see is to remove bo->offset altogether and move that into a helper the drivers can call on demand. -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
