mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Ma Ke <make24@iscas.ac.cn>,
	linux-kselftest@vger.kernel.org,
	Amer Al Shanawany <amer.shanawany@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andy Lutomirski <luto@kernel.org>, Kees Cook <kees@kernel.org>,
	Muhammad Usama Anjum <usama.anjum@collabora.com>,
	Shuah Khan <shuah@kernel.org>,
	Swarup Laxman Kotiaklapudi <swarupkotikalapudi@gmail.com>
Cc: kernel-janitors@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Julia Lawall <julia.lawall@inria.fr>
Subject: Re: [PATCH v3] selftests/capabilities: Fix possible file leak in copy_fromat_to
Date: Mon, 1 Jul 2024 10:01:13 +0200	[thread overview]
Message-ID: <a194b5d3-d3f8-48a4-a010-d98381107b80@web.de> (raw)
In-Reply-To: <20240630130038.3671507-1-make24@iscas.ac.cn>

>                                        … 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

  parent reply	other threads:[~2024-07-01  8:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-30 13:00 Ma Ke
2024-07-01  6:12 ` Muhammad Usama Anjum
2024-07-01  8:01 ` Markus Elfring [this message]
2024-07-02 16:22 ` Shuah Khan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a194b5d3-d3f8-48a4-a010-d98381107b80@web.de \
    --to=markus.elfring@web.de \
    --cc=akpm@linux-foundation.org \
    --cc=amer.shanawany@gmail.com \
    --cc=julia.lawall@inria.fr \
    --cc=kees@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=make24@iscas.ac.cn \
    --cc=shuah@kernel.org \
    --cc=swarupkotikalapudi@gmail.com \
    --cc=usama.anjum@collabora.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®