kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>,
	Pratyush Yadav <pratyush@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH next] liveupdate: luo_file: don't use invalid list iterator
Date: Fri, 28 Nov 2025 12:49:02 +0200	[thread overview]
Message-ID: <aSl-HhDCCjax-XrF@kernel.org> (raw)
In-Reply-To: <aSlMc4SS09Re4_xn@stanley.mountain>

On Fri, Nov 28, 2025 at 10:17:07AM +0300, Dan Carpenter wrote:
> If we exit a list_for_each_entry() without hitting a break then the
> list iterator points to an offset from the list_head.  It's a
> non-NULL but invalid pointer and dereferencing it isn't allowed.
> 
> Introduce a new "found" variable to test instead.
> 
> Fixes: 3ee1d673194e ("liveupdate: luo_file: implement file systems callbacks")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/r/202511280420.y9O4fyhX-lkp@intel.com/
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>

Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>

> ---
> Presumably, this going to be folded into the original patch.  I just
> added the tags because they are harmless.
> 
>  kernel/liveupdate/luo_file.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/liveupdate/luo_file.c b/kernel/liveupdate/luo_file.c
> index fca3806dae28..86b4d274d9aa 100644
> --- a/kernel/liveupdate/luo_file.c
> +++ b/kernel/liveupdate/luo_file.c
> @@ -561,17 +561,20 @@ int luo_retrieve_file(struct luo_file_set *file_set, u64 token,
>  {
>  	struct liveupdate_file_op_args args = {0};
>  	struct luo_file *luo_file;
> +	bool found = false;
>  	int err;
>  
>  	if (list_empty(&file_set->files_list))
>  		return -ENOENT;
>  
>  	list_for_each_entry(luo_file, &file_set->files_list, list) {
> -		if (luo_file->token == token)
> +		if (luo_file->token == token) {
> +			found = true;
>  			break;
> +		}
>  	}
>  
> -	if (luo_file->token != token)
> +	if (!found)
>  		return -ENOENT;
>  
>  	guard(mutex)(&luo_file->mutex);
> -- 
> 2.51.0
> 

-- 
Sincerely yours,
Mike.

  reply	other threads:[~2025-11-28 10:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-28  7:17 [PATCH next] liveupdate: luo_file: don't use invalid list iterator Dan Carpenter
2025-11-28 10:49 ` Mike Rapoport [this message]
2025-11-28 14:38 ` Pasha Tatashin
2025-11-28 16:01   ` Pasha Tatashin

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=aSl-HhDCCjax-XrF@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=dan.carpenter@linaro.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).