[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190121110120.27003-2-christian@brauner.io>
Date: Mon, 21 Jan 2019 12:01:20 +0100
From: Christian Brauner <christian@...uner.io>
To: gregkh@...uxfoundation.org, tkjos@...roid.com,
devel@...verdev.osuosl.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: tkjos@...gle.com, Christian Brauner <christian@...uner.io>
Subject: [PATCH 2/2] 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 <christian@...uner.io>
---
include/uapi/linux/android/binderfs.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/uapi/linux/android/binderfs.h b/include/uapi/linux/android/binderfs.h
index b41628b77120..87410477aea9 100644
--- 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;
};
/**
--
2.19.1
Powered by blists - more mailing lists