UPSTREAM: binderfs: use __u32 for device numbers

We allow more then 255 binderfs binder devices to be created since there are workloads that require more than that. If we use __u8 we'll overflow after 255. So let's use a __u32. Note that there's no released kernel with binderfs out there so this is not a regression. Signed-off-by: Christian Brauner <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> (cherry picked from commit 7d0174065f4903fb0ce0bab3d5047284faa7226d) Bug: 228263403 Signed-off-by: Carlos Llamas <[email protected]> Change-Id: If143c0d6511946fac6349c5db7c013535950de4a
Xtended-Devices · Apr 7, 2022 · 1848ba7 · 1848ba7
1 parent b5814a7
commit 1848ba7
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/include/uapi/linux/android/binderfs.h b/include/uapi/linux/android/binderfs.h
@@ -22,8 +22,8 @@
  */
 struct binderfs_device {
 	char name[BINDERFS_MAX_NAME + 1];
-	__u8 major;
-	__u8 minor;
+	__u32 major;
+	__u32 minor;
 };
 
 /**