From: Uladzislau Rezki <urezki@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
Uladzislau Rezki <urezki@gmail.com>,
Lorenzo Stoakes <lstoakes@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Baoquan He <bhe@redhat.com>
Subject: Re: [patch 5/6] mm/vmalloc: Add missing READ/WRITE_ONCE() annotations
Date: Wed, 24 May 2023 11:15:05 +0200 [thread overview]
Message-ID: <ZG3VmcqyKlS15kQn@pc636> (raw)
In-Reply-To: <20230523140002.799808756@linutronix.de>
On Tue, May 23, 2023 at 04:02:15PM +0200, Thomas Gleixner wrote:
> purge_fragmented_blocks() accesses vmap_block::free and vmap_block::dirty
> lockless for a quick check.
>
> Add the missing READ/WRITE_ONCE() annotations.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> ---
> mm/vmalloc.c | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
>
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -2093,9 +2093,9 @@ static bool purge_fragmented_block(struc
> return false;
>
> /* prevent further allocs after releasing lock */
> - vb->free = 0;
> + WRITE_ONCE(vb->free, 0);
> /* prevent purging it again */
> - vb->dirty = VMAP_BBMAP_BITS;
> + WRITE_ONCE(vb->dirty, VMAP_BBMAP_BITS);
> vb->dirty_min = 0;
> vb->dirty_max = VMAP_BBMAP_BITS;
> spin_lock(&vbq->lock);
> @@ -2123,7 +2123,10 @@ static void purge_fragmented_blocks(int
>
> rcu_read_lock();
> list_for_each_entry_rcu(vb, &vbq->free, free_list) {
> - if (!(vb->free + vb->dirty == VMAP_BBMAP_BITS && vb->dirty != VMAP_BBMAP_BITS))
> + unsigned long free = READ_ONCE(vb->free);
> + unsigned long dirty = READ_ONCE(vb->dirty);
> +
> + if (!(free + dirty == VMAP_BBMAP_BITS && dirty != VMAP_BBMAP_BITS))
> continue;
>
> spin_lock(&vb->lock);
> @@ -2231,7 +2234,7 @@ static void vb_free(unsigned long addr,
> vb->dirty_min = min(vb->dirty_min, offset);
> vb->dirty_max = max(vb->dirty_max, offset + (1UL << order));
>
> - vb->dirty += 1UL << order;
> + WRITE_ONCE(vb->dirty, vb->dirty + (1UL << order));
> if (vb->dirty == VMAP_BBMAP_BITS) {
> BUG_ON(vb->free);
> spin_unlock(&vb->lock);
>
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
--
Uladzislau Rezki
next prev parent reply other threads:[~2023-05-24 9:15 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 14:02 [patch 0/6] mm/vmalloc: Assorted fixes and improvements Thomas Gleixner
2023-05-23 14:02 ` [patch 1/6] mm/vmalloc: Prevent stale TLBs in fully utilized blocks Thomas Gleixner
2023-05-23 15:17 ` Christoph Hellwig
2023-05-23 16:40 ` Thomas Gleixner
2023-05-23 16:47 ` Uladzislau Rezki
2023-05-23 19:18 ` Lorenzo Stoakes
2023-05-24 9:19 ` Uladzislau Rezki
2023-05-24 9:25 ` Baoquan He
2023-05-24 9:51 ` Thomas Gleixner
2023-05-24 11:24 ` Baoquan He
2023-05-24 11:26 ` Baoquan He
2023-05-24 11:36 ` Uladzislau Rezki
2023-05-24 12:49 ` Thomas Gleixner
2023-05-24 12:44 ` Thomas Gleixner
2023-05-24 13:41 ` Baoquan He
2023-05-24 14:31 ` Thomas Gleixner
2023-05-24 9:32 ` Baoquan He
2023-05-24 9:52 ` Thomas Gleixner
2023-05-24 14:10 ` Baoquan He
2023-05-24 14:35 ` Thomas Gleixner
2023-05-23 14:02 ` [patch 2/6] mm/vmalloc: Avoid iterating over per CPU vmap blocks twice Thomas Gleixner
2023-05-23 15:21 ` Christoph Hellwig
2023-05-23 14:02 ` [patch 3/6] mm/vmalloc: Prevent flushing dirty space over and over Thomas Gleixner
2023-05-23 15:27 ` Christoph Hellwig
2023-05-23 16:10 ` Thomas Gleixner
2023-05-24 9:43 ` Baoquan He
2023-05-23 14:02 ` [patch 4/6] mm/vmalloc: Check free space in vmap_block lockless Thomas Gleixner
2023-05-23 15:29 ` Christoph Hellwig
2023-05-23 16:17 ` Thomas Gleixner
2023-05-24 9:20 ` Uladzislau Rezki
2023-05-23 14:02 ` [patch 5/6] mm/vmalloc: Add missing READ/WRITE_ONCE() annotations Thomas Gleixner
2023-05-24 9:15 ` Uladzislau Rezki [this message]
2023-05-23 14:02 ` [patch 6/6] mm/vmalloc: Dont purge usable blocks unnecessarily Thomas Gleixner
2023-05-23 15:30 ` Christoph Hellwig
2023-05-24 10:34 ` Baoquan He
2023-05-24 12:55 ` Thomas Gleixner
2023-05-23 16:24 ` [patch 0/6] mm/vmalloc: Assorted fixes and improvements Uladzislau Rezki
2023-05-23 17:33 ` Thomas Gleixner
2023-05-23 17:39 ` Thomas Gleixner
2023-05-23 17:48 ` Uladzislau Rezki
2023-05-23 17:51 ` Uladzislau Rezki
2023-05-23 17:55 ` Uladzislau Rezki
2023-05-23 18:40 ` Thomas Gleixner
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=ZG3VmcqyKlS15kQn@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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