[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected. No action required from the submitter.
The upstream commit SHA1 provided is correct: 170d1a3738908eef6a0dbf378ea77fb4ae8e294d
Status in newer kernel trees: 6.14.y | Present (different SHA1: c8f9ccac8a5b)
Note: The patch differs from the upstream commit: --- 1: 170d1a3738908 ! 1: 1eec0d8c91a39 binder: fix offset calculation in debug log @@ Metadata ## Commit message ## binder: fix offset calculation in debug log
+ commit 170d1a3738908eef6a0dbf378ea77fb4ae8e294d upstream. + The vma start address should be substracted from the buffer's user data address and not the other way around.
@@ Commit message Reviewed-by: Tiffany Y. Yang ynaffit@google.com Link: https://lore.kernel.org/r/20250325184902.587138-1-cmllamas@google.com Signed-off-by: Greg Kroah-Hartman gregkh@linuxfoundation.org + [cmllamas: fix conflicts due to alloc->buffer renaming] + Signed-off-by: Carlos Llamas cmllamas@google.com
## drivers/android/binder.c ## @@ drivers/android/binder.c: static void print_binder_transaction_ilocked(struct seq_file *m, seq_printf(m, " node %d", buffer->target_node->debug_id); seq_printf(m, " size %zd:%zd offset %lx\n", buffer->data_size, buffer->offsets_size, -- proc->alloc.vm_start - buffer->user_data); -+ buffer->user_data - proc->alloc.vm_start); +- proc->alloc.buffer - buffer->user_data); ++ buffer->user_data - proc->alloc.buffer); }
static void print_binder_work_ilocked(struct seq_file *m, ---
Results of testing on various branches:
| Branch | Patch Apply | Build Test | |---------------------------|-------------|------------| | stable/linux-6.12.y | Success | Success |