From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Dave Hansen <dave.hansen@intel.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
viro@zeniv.linux.org.uk, david@redhat.com,
akpm@linux-foundation.org, aarcange@redhat.com,
linux-mm@kvack.org, frankja@linux.ibm.com, sfr@canb.auug.org.au,
jhubbard@nvidia.com, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org, jack@suse.cz, kirill@shutemov.name,
peterz@infradead.org, sean.j.christopherson@intel.com,
Ulrich.Weigand@de.ibm.com
Subject: Re: [PATCH v2 1/1] fs/splice: add missing callback for inaccessible pages
Date: Tue, 5 May 2020 16:49:54 +0200 [thread overview]
Message-ID: <d31af5af-91fd-a29e-2985-78b61261bc77@de.ibm.com> (raw)
In-Reply-To: <20200505143300.GA14113@oc3748833570.ibm.com>
On 05.05.20 16:33, Ulrich Weigand wrote:
> On Tue, May 05, 2020 at 04:03:00PM +0200, Christian Borntraeger wrote:
>>> Just looked at
>>> commit 88b1a17dfc3ed7728316478fae0f5ad508f50397 mm: add 'try_get_page()' helper function
>>>
>>> which says:
>>> Also like 'get_page()', you can't use this function unless you already
>>> had a reference to the page. The intent is that you can use this
>>> exactly like get_page(), but in situations where you want to limit the
>>> maximum reference count.
>>>
>>> The code currently does an unconditional WARN_ON_ONCE() if we ever hit
>>> the reference count issues (either zero or negative), as a notification
>>> that the conditional non-increment actually happened.
>>>
>>> If try_get_page must not be called with an existing reference, that means
>> s/not//
>>> that when we call it the page reference is already higher and our freeze
>>> will never succeed. That would imply that we cannot trigger this. No?
>
> Well, my understanding is that the "existing" reference may be one of the
> references that is expected by our freeze code, in particular in gup the
> existing reference is simply the one from the pte. So in this case our
> freeze *would* succeeed.
If thats the case then "<0" looks indeed better than "<=0" for the check.
I think try_get_page was never meant to exclude a parallel page_ref_freeze/unfreeze.
next prev parent reply other threads:[~2020-05-05 14:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 14:38 Claudio Imbrenda
2020-04-30 20:04 ` Christian Borntraeger
2020-04-30 22:06 ` Dave Hansen
2020-04-30 22:20 ` Dave Hansen
2020-05-01 7:18 ` Christian Borntraeger
2020-05-01 16:32 ` Dave Hansen
2020-05-04 13:41 ` Ulrich Weigand
2020-05-05 12:34 ` Dave Hansen
2020-05-05 13:55 ` Ulrich Weigand
2020-05-05 14:01 ` Christian Borntraeger
2020-05-05 14:03 ` Christian Borntraeger
2020-05-05 14:33 ` Ulrich Weigand
2020-05-05 14:49 ` Christian Borntraeger [this message]
2020-05-05 14:57 ` Dave Hansen
2020-05-05 14:00 ` Christian Borntraeger
2020-05-05 14:24 ` Dave Hansen
2020-05-05 14:31 ` Christian Borntraeger
2020-05-05 14:34 ` Dave Hansen
2020-05-05 14:39 ` Christian Borntraeger
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=d31af5af-91fd-a29e-2985-78b61261bc77@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jack@suse.cz \
--cc=jhubbard@nvidia.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sean.j.christopherson@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=uweigand@de.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/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