mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: IFsuse <ifsuse14@gmail.com>
To: Jakob Koschel <jakobkoschel@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Arve Hjønnevåg" <arve@android.com>,
	"Todd Kjos" <tkjos@android.com>,
	"Martijn Coenen" <maco@android.com>,
	"Joel Fernandes" <joel@joelfernandes.org>,
	"Christian Brauner" <brauner@kernel.org>,
	"Hridya Valsaraju" <hridya@google.com>,
	"Suren Baghdasaryan" <surenb@google.com>,
	linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
	"Mike Rapoport" <rppt@kernel.org>,
	"Brian Johannesmeyer" <bjohannesmeyer@gmail.com>,
	"Cristiano Giuffrida" <c.giuffrida@vu.nl>,
	"Bos, H.J." <h.j.bos@vu.nl>
Subject: Re: [PATCH] staging: android: ashmem: remove usage of list iterator after the loop body
Date: Sun, 20 Nov 2022 18:05:20 +0800	[thread overview]
Message-ID: <a62fcd23-068d-38f0-f426-d2511e23ed73@gmail.com> (raw)
In-Reply-To: <20220331213934.866804-1-jakobkoschel@gmail.com>


在 2022/4/1 上午5:39, Jakob Koschel 写道:
> In preparation to limit the scope of a list iterator to the list
> traversal loop, use a dedicated pointer to point to the found element
> [1].
>
> Before, the code implicitly used the head when no element was found
> when using &pos->list. Since the new variable is only set if an
> element was found, the head needs to be used explicitly if the
> variable is NULL.
>
> Link: https://lore.kernel.org/all/CAHk-=wgRr_D8CB-D9Kg-c=EHreAsk5SqXPwr9Y7k9sA6cWXJ6w@mail.gmail.com/ [1]
> Signed-off-by: Jakob Koschel <jakobkoschel@gmail.com>
> ---
>   drivers/staging/android/ashmem.c | 21 ++++++++++++---------
>   1 file changed, 12 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c
> index ddbde3f8430e..a1e245827cf6 100644
> --- a/drivers/staging/android/ashmem.c
> +++ b/drivers/staging/android/ashmem.c
> @@ -703,30 +703,33 @@ static int ashmem_pin(struct ashmem_area *asma, size_t pgstart, size_t pgend,
>   static int ashmem_unpin(struct ashmem_area *asma, size_t pgstart, size_t pgend,
>   			struct ashmem_range **new_range)
>   {
> -	struct ashmem_range *range, *next;
> +	struct ashmem_range *range = NULL, *iter, *next;
>   	unsigned int purged = ASHMEM_NOT_PURGED;
>   
>   restart:
> -	list_for_each_entry_safe(range, next, &asma->unpinned_list, unpinned) {
> +	list_for_each_entry_safe(iter, next, &asma->unpinned_list, unpinned) {
>   		/* short circuit: this is our insertion point */
> -		if (range_before_page(range, pgstart))
> +		if (range_before_page(iter, pgstart)) {
> +			range = iter;
>   			break;
> +		}
>   
>   		/*
>   		 * The user can ask us to unpin pages that are already entirely
>   		 * or partially pinned. We handle those two cases here.
>   		 */
> -		if (page_range_subsumed_by_range(range, pgstart, pgend))
> +		if (page_range_subsumed_by_range(iter, pgstart, pgend))
>   			return 0;
> -		if (page_range_in_range(range, pgstart, pgend)) {
> -			pgstart = min(range->pgstart, pgstart);
> -			pgend = max(range->pgend, pgend);
> -			purged |= range->purged;
> -			range_del(range);
> +		if (page_range_in_range(iter, pgstart, pgend)) {
> +			pgstart = min(iter->pgstart, pgstart);
> +			pgend = max(iter->pgend, pgend);
> +			purged |= iter->purged;
> +			range_del(iter);
>   			goto restart;
>   		}
>   	}
>   
> +	range = list_prepare_entry(range, &asma->unpinned_list, unpinned);
>   	range_alloc(asma, range, purged, pgstart, pgend, new_range);
>   	return 0;
>   }
>
> base-commit: f82da161ea75dc4db21b2499e4b1facd36dab275

      parent reply	other threads:[~2022-11-20 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 21:39 Jakob Koschel
2022-04-01  5:38 ` Greg Kroah-Hartman
2022-04-01  6:50   ` Jakob Koschel
2022-11-20 10:05 ` IFsuse [this message]

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=a62fcd23-068d-38f0-f426-d2511e23ed73@gmail.com \
    --to=ifsuse14@gmail.com \
    --cc=arve@android.com \
    --cc=bjohannesmeyer@gmail.com \
    --cc=brauner@kernel.org \
    --cc=c.giuffrida@vu.nl \
    --cc=gregkh@linuxfoundation.org \
    --cc=h.j.bos@vu.nl \
    --cc=hridya@google.com \
    --cc=jakobkoschel@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=maco@android.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=tkjos@android.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®