[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200515144512.GB2836808@arch-x1c3>
Date: Fri, 15 May 2020 15:45:12 +0100
From: Emil Velikov <emil.velikov@...labora.com>
To: Sebastian Reichel <sebastian.reichel@...labora.com>
Cc: Sebastian Reichel <sre@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J . Wysocki" <rafael@...nel.org>, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel@...labora.com
Subject: Re: [PATCHv1 01/19] kobject: increase allowed number of uevent
variables
On 2020/05/13, Sebastian Reichel wrote:
> SBS battery driver exposes 32 power supply properties now,
> which will result in uevent failure on (un)plugging the
> battery. Other drivers (e.g. bq27xxx) are also coming close
> to this limit, so increase it.
>
> Signed-off-by: Sebastian Reichel <sebastian.reichel@...labora.com>
> ---
> include/linux/kobject.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/kobject.h b/include/linux/kobject.h
> index e2ca0a292e21..75e822569e39 100644
> --- a/include/linux/kobject.h
> +++ b/include/linux/kobject.h
> @@ -29,7 +29,7 @@
> #include <linux/uidgid.h>
>
> #define UEVENT_HELPER_PATH_LEN 256
> -#define UEVENT_NUM_ENVP 32 /* number of env pointers */
> +#define UEVENT_NUM_ENVP 64 /* number of env pointers */
To be on the safe side I've checked systemd/udev. It's using ordered hashmap,
so it's perfectly capable of handling the extra entries.
Reviewed-by: Emil Velikov <emil.velikov@...labora.com>
-Emil
Powered by blists - more mailing lists