Re: ntdll: Return STATUS_SUCCESS from SetInformationJobObject

[Nikolay Sivov]

I don't think it's a good idea to always claim success. It might be 
better to actually store those UILIMIT flags (probably by extending 
set_job_limits ). Alternatively if you don't want to store those for 
some reason you can return success for this class only while keeping a 
fixme, but not for all unimplemented classes.

ntdll: Return STATUS_SUCCESS from SetInformationJobObject

[Andrew Cook]

On Sat, 2015-04-04 at 10:10 +0300, Nikolay Sivov wrote:
> I don't think it's a good idea to always claim success. It might be 
> better to actually store those UILIMIT flags (probably by extending 
> set_job_limits ). Alternatively if you don't want to store those for 
> some reason you can return success for this class only while keeping a 
> fixme, but not for all unimplemented classes.

Long term would there be any interest in actually implementing job
limits? most are security or resource limits, not expected in normal
execution. process breakaway, the exception, is implemented.