Conversation
rw

Richard Weinberger

Hunting down bugs on embedded systems is not always fun. That one was.

https://sigma-star.at/blog/2025/06/deep-down-the-rabbit-hole-bash-overlayfs-and-a-30-year-old-surprise/
3
10
12
manut@mountains.social

Manuel Traut 🐧

Reply to @rw

@rw wouldn’t it be fine to change the default to no broken cwd in bash’s configure.ac if cross compilation and glibc was detected? Instead of hacking each and every Linux cross compile setup/tooling..

1
0
0
rw

Richard Weinberger

Reply to @manut@mountains.social
@manut sure. I'd go so far and suggest removing the getcwd() fallback at all.
2
0
1
agraf@fosstodon.org

Alexander Graf

Reply to @rw

@rw @manut I agree 😁. Now that you've analyzed all of this and drew conclusions, what's keeping you from posting a patch to bash to remove the broken getcwd fallback? 😎

1
0
0
manut@mountains.social

Manuel Traut 🐧

Reply to @rw

@rw wouldn’t this break bootstrapping an OS without a getcwd implementation? Not sure if this is relevant as of today..

1
0
0
rw

Richard Weinberger

Reply to @manut@mountains.social
@manut I meant for Linux. Having the fallback available on Linux makes no sense.
1
0
0
rw

Richard Weinberger

Reply to @agraf@fosstodon.org
@agraf @manut
I did report the issue already:
https://lists.gnu.org/archive/html/bug-bash/2025-06/msg00149.html

Given the responses so far, I'm not sure whether I want to continue this path.
1
0
0
manut@mountains.social

Manuel Traut 🐧

Reply to @rw

@rw this would be fine. Thanks for taking care and sharing!

0
0
0
agraf@fosstodon.org

Alexander Graf

Reply to @rw

@rw @manut Definitely worthwhile. Don't feed the trolls 😁. That dude is just a random person with too much time on theor hands. If you send a patch, the conversation will go differently. In the patch, stress that it's broken in multiple ways (overlayfs & errno) and effectively a completely untested code path that clearly saw no real life use because otherwise at least the errno thing would have been caught by now.

0
0
1
stefanct@chaos.social

stefanct

Reply to @rw

@rw "with and inode"

1
0
0
rw

Richard Weinberger

Reply to @stefanct@chaos.social
@stefanct Thx!
0
0
0
stefanct@chaos.social

stefanct

Reply to @rw

@rw i don't want to throw shade at all, just curious... do you roll your own build environment or was it another well known one?

1
0
0
rw

Richard Weinberger

Reply to @stefanct@chaos.social
@stefanct It's an in-house solution developed and maintained by one of my customers.
0
0
1
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: