From: Cesar Eduardo Barros <cesarb@cesarb.eti.br>
To: Andrey Konovalov <andreyknvl@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov@parallels.com>,
Hugh Dickins <hughd@google.com>,
Miklos Szeredi <mszeredi@suse.cz>, Jason Low <jason.low2@hp.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Dmitry Vyukov <dvyukov@google.com>,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>
Subject: Re: Potential data race in SyS_swapon
Date: Fri, 7 Aug 2015 20:32:32 -0300 [thread overview]
Message-ID: <55C54010.4000904@cesarb.eti.br> (raw)
In-Reply-To: <CAAeHK+w7bQtAUAWFrcqE5Gf8t8nZoHim6iXg1axXdC_bVmrNDw@mail.gmail.com>
Em 07-08-2015 13:14, Andrey Konovalov escreveu:
> Hi!
>
> We are working on a dynamic data race detector for the Linux kernel
> called KernelThreadSanitizer (ktsan)
> (https://github.com/google/ktsan/wiki).
>
> While running ktsan on the upstream revision 21bdb584af8c with trinity
> we got a few reports from SyS_swapon, here is one of them:
[...]
> The race is happening when accessing the swap_file field of a
> swap_info_struct struct.
>
> 2392 for (i = 0; i < nr_swapfiles; i++) {
> 2393 struct swap_info_struct *q = swap_info[i];
> 2394
> 2395 if (q == p || !q->swap_file)
> 2396 continue;
> 2397 if (mapping == q->swap_file->f_mapping) {
> 2398 error = -EBUSY;
> 2399 goto bad_swap;
> 2400 }
> 2401 }
>
> 2539 spin_lock(&swap_lock);
> 2540 p->swap_file = NULL;
> 2541 p->flags = 0;
> 2542 spin_unlock(&swap_lock);
There's another (more important) place which sets the swap_file field to
NULL, it's within swapoff. It's also protected by swap_lock.
> Since the swap_lock lock is not taken in the first snippet, it's
> possible for q->swap_file to be assigned to NULL and reloaded between
> executing lines 2395 and 2397, which might lead to a null pointer
> dereference.
I agree with that analysis. It should be possible to hit by racing
swapon of a file with swapoff of another.
> Looks like the swap_lock should be taken when iterating through the
> swap_info array on lines 2392 - 2401.
I'd take that lock a couple of lines earlier, so that every place that
sets the swap_file field on a swap_info_struct is behind swap_lock, for
simplicity.
--
Cesar Eduardo Barros
cesarb@cesarb.eti.br
--
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:[~2015-08-07 23:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 16:14 Andrey Konovalov
2015-08-07 23:32 ` Cesar Eduardo Barros [this message]
2015-08-17 23:22 ` Hugh Dickins
2015-08-18 0:34 ` [PATCH] mm: fix potential " Hugh Dickins
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=55C54010.4000904@cesarb.eti.br \
--to=cesarb@cesarb.eti.br \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=jason.low2@hp.com \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=mszeredi@suse.cz \
--cc=vdavydov@parallels.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