mirror of
				https://github.com/RGBCube/serenity
				synced 2025-10-31 22:02:44 +00:00 
			
		
		
		
	Kernel: Add a comment explaining an alternate path in Process::exec()
I had to look at this for a moment before I realized that sys$execve() and the spawning of /bin/SystemServer at boot are taking two different paths out of exec(). Add a comment to help the next person looking at it. :^)
This commit is contained in:
		
							parent
							
								
									5d06ab6531
								
							
						
					
					
						commit
						fe2e25edad
					
				
					 1 changed files with 3 additions and 0 deletions
				
			
		|  | @ -848,6 +848,9 @@ KResult Process::exec(String path, Vector<String> arguments, Vector<String> envi | ||||||
|         VERIFY_NOT_REACHED(); |         VERIFY_NOT_REACHED(); | ||||||
|     } |     } | ||||||
| 
 | 
 | ||||||
|  |     // NOTE: This code path is taken in the non-syscall case, i.e when the kernel spawns
 | ||||||
|  |     //       a userspace process directly (such as /bin/SystemServer on startup)
 | ||||||
|  | 
 | ||||||
|     if (prev_flags & 0x200) |     if (prev_flags & 0x200) | ||||||
|         sti(); |         sti(); | ||||||
|     Processor::leave_critical(); |     Processor::leave_critical(); | ||||||
|  |  | ||||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue
	
	 Andreas Kling
						Andreas Kling