[Buildroot] [Bug 12866] New: should we be disabling bash executable path caching?

[Buildroot] [Bug 12866] New: should we be disabling bash executable path caching?

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=12866

            Bug ID: 12866
           Summary: should we be disabling bash executable path caching?
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: matthew.weber at rockwellcollins.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

I'm not sure if there is a use case (yet), maybe with parallel builds if the
host folder contents ends up with per package staging?

https://unix.stackexchange.com/questions/5609/how-do-i-clear-bashs-cache-of-paths-to-executables/218681#218681

We ran into it when we were testing the internal toolchain of buildroot to be
relocatable and the "mv" executable was used to rename the host folder.  Then
we used "mv" again to rename the host folder back. For the first "mv" it used
the Buildroot host/bin/mv and then for the second "mv", bash tried to again use
the same instead of continuing to traverse to /bin/mv which was in the path and
the output of "which mv" at that point in the script.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 12866] should we be disabling bash executable path caching?

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=12866

--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
I don't quite follow what Buildroot can do here, i.e how would we disable this
bash caching functionnality from the system-provided bash? I'm not even sure it
makes sense for us to do this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 12866] should we be disabling bash executable path caching?

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=12866

--- Comment #2 from Matt Weber <matthew.weber@rockwellcollins.com> ---
Thinking about it a little more, the actual shell script would need to set 'set
+h' but my understanding is the executable hash table (for quick lookup after a
commend is executed the first time) is just local to the current script's
context.  So to cause an issue, you would have to call the same command twice
in the same script and move the location of the executable without updating the
PATH.  That doesn't sound normal.  I'll close this bug :-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 12866] should we be disabling bash executable path caching?

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=12866

Matt Weber <matthew.weber@rockwellcollins.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

-- 
You are receiving this mail because:
You are on the CC list for the bug.