From d562ca78aa713d186e83f05061c0aed88e200bcd Mon Sep 17 00:00:00 2001 From: Andrew Boie Date: Tue, 4 Dec 2012 15:47:20 -0800 Subject: [PATCH] ueventd: Increase uevent buffer size As it turns out, no, 64K is not enough. A device provisioning tool was generating many uevents as it manipulated the GPT, causing events near the end of the process (including events as a result of the final BLKRRPART ioctl()) to get lost. It's not clear what the best value for this should be, but increasing to 256K fixed the problem in this case. Change-Id: I4883b34e96c89e8a6fa581bc9cd121bb021b5694 Signed-off-by: Andrew Boie --- init/devices.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/init/devices.c b/init/devices.c index dd875d655..b07a1a6a1 100644 --- a/init/devices.c +++ b/init/devices.c @@ -881,8 +881,8 @@ void device_init(void) sehandle = selinux_android_file_context_handle(); } - /* is 64K enough? udev uses 16MB! */ - device_fd = uevent_open_socket(64*1024, true); + /* is 256K enough? udev uses 16MB! */ + device_fd = uevent_open_socket(256*1024, true); if(device_fd < 0) return;