The GNU Hurd - Patches: patch #6844, fix a bug in init: initialize...
You are not allowed to post comments on this tracker with your current authentication level.
patch #6844: fix a bug in init: initialize 'flags' in reboot_system
Submitter: | Zheng Da <zhengda> | ||
Submitted: | Tue 02 Jun 2009 08:47:27 AM UTC | ||
Category: | other Hurd | Priority: | 5 - Normal |
Status: | Works For Me | Privacy: | Public |
Assigned to: | None | Open/Closed: | Open |
Planned Release: | None | ||
Wiki-like text discussion box: |
|
Attached Files
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2009-06-02 | zhengda | Attached File | - | Added init.diff, #18216 |
Powered by Savane 3.13-f8d8.
Corresponding source code
We should initialize 'flags' in reboot_system.
The only information we need to get from proc_getprocinfo is the state of the process. 'flags = 0' is very enough to do the job and it can make proc_getprocinfo less likely to fail.
The Mach in my system somehow doesn't support the TASK_EVENTS_INFO type of information. Without the initialization of 'flags', it is possible that proc_getprocinfo returns error, which results in the failure to shut down the subhurd.