From: "Huang\, Ying" <ying.huang@intel.com>
To: Daniel Jordan <daniel.m.jordan@oracle.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Shaohua Li <shli@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Omar Sandoval <osandov@fb.com>, Tejun Heo <tj@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
linux-mm@kvack.org, kernel-janitors@vger.kernel.org,
andrea.parri@amarulasolutions.com
Subject: Re: [PATCH] mm, swap: Potential NULL dereference in get_swap_page_of_type()
Date: Mon, 14 Jan 2019 10:12:25 +0800 [thread overview]
Message-ID: <87r2dgm1h2.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20190111174128.oak64htbntvp7j6y@ca-dmjordan1.us.oracle.com> (Daniel Jordan's message of "Fri, 11 Jan 2019 09:41:28 -0800")
Hi, Daniel,
Daniel Jordan <daniel.m.jordan@oracle.com> writes:
> On Fri, Jan 11, 2019 at 12:59:19PM +0300, Dan Carpenter wrote:
>> Smatch complains that the NULL checks on "si" aren't consistent. This
>> seems like a real bug because we have not ensured that the type is
>> valid and so "si" can be NULL.
>>
>> Fixes: ec8acf20afb8 ("swap: add per-partition lock for swapfile")
>> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>> ---
>> mm/swapfile.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/mm/swapfile.c b/mm/swapfile.c
>> index f0edf7244256..21e92c757205 100644
>> --- a/mm/swapfile.c
>> +++ b/mm/swapfile.c
>> @@ -1048,9 +1048,12 @@ swp_entry_t get_swap_page_of_type(int type)
>> struct swap_info_struct *si;
>> pgoff_t offset;
>>
>> + if (type >= nr_swapfiles)
>> + goto fail;
>> +
>
> As long as we're worrying about NULL, I think there should be an smp_rmb here
> to ensure swap_info[type] isn't NULL in case of an (admittedly unlikely) racing
> swapon that increments nr_swapfiles. See smp_wmb in alloc_swap_info and the
> matching smp_rmb's in the file. And READ_ONCE's on either side of the barrier
> per LKMM.
I think you are right here. And smp_rmb() for nr_swapfiles are missing
in many other places in swapfile.c too (e.g. __swap_info_get(),
swapdev_block(), etc.).
In theory, I think we need to fix this.
Best Regards,
Huang, Ying
> I'm adding Andrea (randomly selected from the many LKMM folks to avoid spamming
> all) who can correct me if I'm wrong about any of this.
>
>> si = swap_info[type];
>> spin_lock(&si->lock);
>> - if (si && (si->flags & SWP_WRITEOK)) {
>> + if (si->flags & SWP_WRITEOK) {
>> atomic_long_dec(&nr_swap_pages);
>> /* This is called for allocating swap entry, not cache */
>> offset = scan_swap_map(si, 1);
>> @@ -1061,6 +1064,7 @@ swp_entry_t get_swap_page_of_type(int type)
>> atomic_long_inc(&nr_swap_pages);
>> }
>> spin_unlock(&si->lock);
>> +fail:
>> return (swp_entry_t) {0};
>> }
>>
>> --
>> 2.17.1
>>
WARNING: multiple messages have this Message-ID
From: "Huang\, Ying" <ying.huang@intel.com>
To: Daniel Jordan <daniel.m.jordan@oracle.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Shaohua Li <shli@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Omar Sandoval <osandov@fb.com>, Tejun Heo <tj@kernel.org>,
Andi Kleen <ak@linux.intel.com>, <linux-mm@kvack.org>,
<kernel-janitors@vger.kernel.org>,
<andrea.parri@amarulasolutions.com>
Subject: Re: [PATCH] mm, swap: Potential NULL dereference in get_swap_page_of_type()
Date: Mon, 14 Jan 2019 10:12:25 +0800 [thread overview]
Message-ID: <87r2dgm1h2.fsf@yhuang-dev.intel.com> (raw)
Message-ID: <20190114021225.D9-nsROMXRD56Hpav9VYtsel2acaYpp_Xkc3KJEFbR4@z> (raw)
In-Reply-To: <20190111174128.oak64htbntvp7j6y@ca-dmjordan1.us.oracle.com> (Daniel Jordan's message of "Fri, 11 Jan 2019 09:41:28 -0800")
Hi, Daniel,
Daniel Jordan <daniel.m.jordan@oracle.com> writes:
> On Fri, Jan 11, 2019 at 12:59:19PM +0300, Dan Carpenter wrote:
>> Smatch complains that the NULL checks on "si" aren't consistent. This
>> seems like a real bug because we have not ensured that the type is
>> valid and so "si" can be NULL.
>>
>> Fixes: ec8acf20afb8 ("swap: add per-partition lock for swapfile")
>> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>> ---
>> mm/swapfile.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/mm/swapfile.c b/mm/swapfile.c
>> index f0edf7244256..21e92c757205 100644
>> --- a/mm/swapfile.c
>> +++ b/mm/swapfile.c
>> @@ -1048,9 +1048,12 @@ swp_entry_t get_swap_page_of_type(int type)
>> struct swap_info_struct *si;
>> pgoff_t offset;
>>
>> + if (type >= nr_swapfiles)
>> + goto fail;
>> +
>
> As long as we're worrying about NULL, I think there should be an smp_rmb here
> to ensure swap_info[type] isn't NULL in case of an (admittedly unlikely) racing
> swapon that increments nr_swapfiles. See smp_wmb in alloc_swap_info and the
> matching smp_rmb's in the file. And READ_ONCE's on either side of the barrier
> per LKMM.
I think you are right here. And smp_rmb() for nr_swapfiles are missing
in many other places in swapfile.c too (e.g. __swap_info_get(),
swapdev_block(), etc.).
In theory, I think we need to fix this.
Best Regards,
Huang, Ying
> I'm adding Andrea (randomly selected from the many LKMM folks to avoid spamming
> all) who can correct me if I'm wrong about any of this.
>
>> si = swap_info[type];
>> spin_lock(&si->lock);
>> - if (si && (si->flags & SWP_WRITEOK)) {
>> + if (si->flags & SWP_WRITEOK) {
>> atomic_long_dec(&nr_swap_pages);
>> /* This is called for allocating swap entry, not cache */
>> offset = scan_swap_map(si, 1);
>> @@ -1061,6 +1064,7 @@ swp_entry_t get_swap_page_of_type(int type)
>> atomic_long_inc(&nr_swap_pages);
>> }
>> spin_unlock(&si->lock);
>> +fail:
>> return (swp_entry_t) {0};
>> }
>>
>> --
>> 2.17.1
>>
next prev parent reply other threads:[~2019-01-14 2:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 9:59 Dan Carpenter
2019-01-11 17:41 ` Daniel Jordan
2019-01-11 23:20 ` Andrea Parri
2019-01-14 22:25 ` Daniel Jordan
2019-01-15 0:23 ` [PATCH] mm, swap: bounds check swap_info accesses to avoid NULL derefs Daniel Jordan
2019-01-15 1:17 ` Andrea Parri
2019-01-30 6:26 ` Andrew Morton
2019-01-31 1:52 ` Daniel Jordan
2019-01-31 2:44 ` [PATCH v2] mm, swap: bounds check swap_info array " Daniel Jordan
2019-01-31 2:48 ` About swapoff race patch (was Re: [PATCH] mm, swap: bounds check swap_info accesses to avoid NULL derefs) Huang, Ying
2019-01-31 20:46 ` Andrew Morton
2019-02-02 7:14 ` Huang, Ying
2019-02-04 21:37 ` Hugh Dickins
2019-02-04 22:26 ` Matthew Wilcox
2019-02-06 0:14 ` Huang, Ying
2019-02-06 0:36 ` Hugh Dickins
2019-02-06 0:58 ` Huang, Ying
2019-02-08 0:28 ` Andrea Parri
2019-02-11 1:02 ` Huang, Ying
2019-01-30 7:28 ` [PATCH] mm, swap: bounds check swap_info accesses to avoid NULL derefs Dan Carpenter
2019-01-31 1:55 ` Daniel Jordan
2019-01-30 9:13 ` Peter Zijlstra
2019-01-31 2:00 ` Daniel Jordan
2019-01-15 0:28 ` [PATCH] mm, swap: Potential NULL dereference in get_swap_page_of_type() Andrea Parri
2019-01-14 2:12 ` Huang, Ying [this message]
2019-01-14 2:12 ` Huang, Ying
2019-01-14 8:43 ` Dan Carpenter
2019-01-14 23:40 ` Daniel Jordan
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=87r2dgm1h2.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrea.parri@amarulasolutions.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel.m.jordan@oracle.com \
--cc=dave.hansen@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osandov@fb.com \
--cc=sfr@canb.auug.org.au \
--cc=shli@kernel.org \
--cc=tj@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