python / python/cpython

use of uninitialized value with msan from subprocess_fork_exec

Open
#91,055 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.10 3.11 3.9 (EOL) stdlib type-feature
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 46899
Nosy @gpshead, @yilei

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2022-03-02.00:48:44.660>
labels = ['type-feature', 'library', '3.9', '3.10', '3.11']
title = 'use of uninitialized value with msan from subprocess_fork_exec'
updated_at = <Date 2022-03-02.00:48:44.660>
user = 'https://github.com/yilei'

bugs.python.org fields:

activity = <Date 2022-03-02.00:48:44.660>
actor = 'yilei'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2022-03-02.00:48:44.660>
creator = 'yilei'
dependencies = []
files = []
hgrepos = []
issue_num = 46899
keywords = []
message_count = 1.0
messages = ['414320']
nosy_count = 2.0
nosy_names = ['gregory.p.smith', 'yilei']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue46899'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names the subprocess_fork_exec entry point and the original BPO 46899 report; start by reading that report and tracing the entry point in CPython. Investigate the MSan uninitialized-value warning and determine the affected subprocess behavior. Done means the warning is resolved and the behavior is covered by appropriate verification.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.