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 <christian@brauner.io> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 7d0174065f4903fb0ce0bab3d5047284faa7226d) Bug: 228263403 Signed-off-by: Carlos Llamas <cmllamas@google.com> Change-Id: If143c0d6511946fac6349c5db7c013535950de4a
This commit is contained in:
parent
22fdca5318
commit
b155e0447d
@ -22,8 +22,8 @@
|
||||
*/
|
||||
struct binderfs_device {
|
||||
char name[BINDERFS_MAX_NAME + 1];
|
||||
__u8 major;
|
||||
__u8 minor;
|
||||
__u32 major;
|
||||
__u32 minor;
|
||||
};
|
||||
|
||||
/**
|
||||
|
Loading…
Reference in New Issue
Block a user