Fixed
Status Update
No update yet.
Comments
en...@google.com
have you actually hit this limit in practice?
gr...@gmail.com
I've hit this limit and that made me question the choice of !28 in this bug report.
The scenario is the following:
- we're deploying unit and functional tests over SSH to non rooted Android devices
- beside executables we're deploying big assets (several GB) over SSH wtih rsync
- we're using SSHDroid which home is /data/data/berserker.android.apps.sshdroid/home
/data/data/berserker.android.apps.sshdroid/home is already 48 characters which is more than a third of the maximum allowed name if you pass an absolute path to dlopen()
Gregory
The scenario is the following:
- we're deploying unit and functional tests over SSH to non rooted Android devices
- beside executables we're deploying big assets (several GB) over SSH wtih rsync
- we're using SSHDroid which home is /data/data/berserker.android.apps.sshdroid/home
/data/data/berserker.android.apps.sshdroid/home is already 48 characters which is more than a third of the maximum allowed name if you pass an absolute path to dlopen()
Gregory
Description
#define SOINFO_NAME_LEN 128
and in struct sofinfo, char name[SOINFO_NAME_LEN];
This is way too short considering PATH_MAX definition:
libc/kernel/uapi/linux/limits.h
#define PATH_MAX 4096
or _POSIX_PATH_MAX
libc/include/machine/posix_limits.h
#define _POSIX_PATH_MAX 256