From: Vlastimil Babka <vbabka@suse.cz>
To: Minchan Kim <minchan@kernel.org>, Junil Lee <junil0814.lee@lge.com>
Cc: ngupta@vflare.org, sergey.senozhatsky.work@gmail.com,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] zsmalloc: fix migrate_zspage-zs_free race condition
Date: Fri, 15 Jan 2016 16:49:40 +0100 [thread overview]
Message-ID: <56991514.9000609@suse.cz> (raw)
In-Reply-To: <20160115143434.GA25332@blaptop.local>
On 01/15/2016 03:34 PM, Minchan Kim wrote:
> On Fri, Jan 15, 2016 at 04:39:11PM +0900, Junil Lee wrote:
>>
>> Signed-off-by: Junil Lee <junil0814.lee@lge.com>
>
> Acked-by: Minchan Kim <minchan@kernel.org>
>
> Below comment.
>
>> ---
>> mm/zsmalloc.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
>> index e7414ce..a24ccb1 100644
>> --- a/mm/zsmalloc.c
>> +++ b/mm/zsmalloc.c
>> @@ -1635,6 +1635,8 @@ static int migrate_zspage(struct zs_pool *pool, struct size_class *class,
>> free_obj = obj_malloc(d_page, class, handle);
>> zs_object_copy(free_obj, used_obj, class);
>> index++;
>> + /* Must not unlock before unpin_tag() */
>
> I want to make comment more clear.
>
> /*
> * record_obj updates handle's value to free_obj and it will invalidate
> * lock bit(ie, HANDLE_PIN_BIT) of handle, which breaks synchronization
> * using pin_tag(e,g, zs_free) so let's keep the lock bit.
> */
>
> Thanks.
Could you please also help making the changelog more clear?
>
>> + free_obj |= BIT(HANDLE_PIN_BIT);
>> record_obj(handle, free_obj);
I think record_obj() should use WRITE_ONCE() or something like that.
Otherwise the compiler is IMHO allowed to reorder this, i.e. first to
assign free_obj to handle, and then add the PIN bit there.
>> unpin_tag(handle);
>> obj_free(pool, class, used_obj);
>> --
>> 2.6.2
>>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-01-15 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 7:39 [PATCH v2] zsmalloc: fix migrate_zspage-zs_free race condition Junil Lee
2016-01-15 14:34 ` Minchan Kim
2016-01-15 15:49 ` Vlastimil Babka [this message]
2016-01-16 4:09 ` Sergey Senozhatsky
2016-01-16 7:44 ` Vlastimil Babka
2016-01-16 8:06 ` Sergey Senozhatsky
2016-01-16 8:16 ` Vlastimil Babka
2016-01-16 10:05 ` Sergey Senozhatsky
2016-01-18 1:02 ` Junil Lee
2016-01-18 6:32 ` Minchan Kim
2016-01-18 7:04 ` Sergey Senozhatsky
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=56991514.9000609@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=junil0814.lee@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@gmail.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;
as well as URLs for NNTP newsgroup(s).