Re: [PATCH v3] selftests/capabilities: Fix possible file leak in copy_fromat_to

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>                                        … openat() and open() initialize
> 'from' and 'to', and only 'from' validated with 'if' statement.

Why do you find such information helpful?


>                                                                 If the
> initialization of variable 'to' fails,

The variable assignment will usually succeed.
A stored return value would eventually indicate a failed function call.


>                                        we should better check the value
> of 'to' and close 'from' to avoid possible file leak. Improve the checking
> of 'from' additionally.

Please split desired changes into separate update steps.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10-rc6#n168


How do you think about to use a summary phrase like “Complete error handling
in copy_fromat_to()”?


Under which circumstances would you become interested to take remaining
patch review concerns better into account?


…
> ---
> Changes in v3:
> - Thank you for your interest in our vulnerability detection method. We
> extract vulnerability characteristics from a known vulnerability and match
> the same characteristics in the project code. As our work is still in
> progress, we are not able to disclose it at this time. …

* In which time range do you plan to publish an official announcement?

* Will similar software research approaches be discussed further?


> - found by customized static analysis tool.
> ---

Would you like to replace a duplicate marker line by a blank line?


Regards,
Markus





[Index of Archives]     [Kernel Development]     [Kernel Announce]     [Kernel Newbies]     [Linux Networking Development]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Device Mapper]

  Powered by Linux