Skip to content

{bp-19394} fs/procfs: fix incorrect environ read for another task under CONFIG_ARCH_ADDRENV - #19611

Merged
xiaoxiang781216 merged 1 commit into
apache:releases/13.0from
jerpelea:bp-19394
Aug 3, 2026
Merged

{bp-19394} fs/procfs: fix incorrect environ read for another task under CONFIG_ARCH_ADDRENV#19611
xiaoxiang781216 merged 1 commit into
apache:releases/13.0from
jerpelea:bp-19394

Conversation

@jerpelea

@jerpelea jerpelea commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Summary

Reading /proc//group/env for another task dereferenced tg_envp under the caller's own address environment instead of the target task's, since tg_envp lives in the target's user heap. Switch to the target's address environment around the traversal, and to the caller's own environment only around the copy into the caller's buffer.

Impact

RELEASE

Testing

CI

…RCH_ADDRENV

Reading /proc/<pid>/group/env for another task dereferenced tg_envp
under the caller's own address environment instead of the target
task's, since tg_envp lives in the target's user heap. Switch to the
target's address environment around the traversal, and to the
caller's own environment only around the copy into the caller's
buffer.

Signed-off-by: liang.huang <liang.huang@houmo.ai>
@jerpelea jerpelea changed the title {Bp 19394} fs/procfs: fix incorrect environ read for another task under CONFIG_ARCH_ADDRENV {bp-19394} fs/procfs: fix incorrect environ read for another task under CONFIG_ARCH_ADDRENV Aug 3, 2026
@github-actions github-actions Bot added Area: File System File System issues Size: S The size of the change in this PR is small labels Aug 3, 2026
@xiaoxiang781216
xiaoxiang781216 merged commit d8740d1 into apache:releases/13.0 Aug 3, 2026
16 of 41 checks passed
@cederom

cederom commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

uhm, merging to releases/13.0 while 13.0.0 is already out?? why not releases/13.0.1 or 13.1.0 or similar? we should use X.Y.Z nomenclature in branches too? :-)

@cederom

cederom commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

@cederom: uhm, merging to releases/13.0 while 13.0.0 is already out?? why not releases/13.0.1 or 13.1.0 or similar? we should use X.Y.Z nomenclature in branches too? :-)

okay releases/13.0 is the branch for 13.0.Z that means next release will be 13.0.1 and these are identified by tags, thank you @jerpelea :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: File System File System issues Size: S The size of the change in this PR is small

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants