From: David Hildenbrand <david@redhat.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH v1 2/5] s390/uv: convert gmap_make_secure() to work on folios
Date: Thu, 11 Apr 2024 11:09:53 +0200 [thread overview]
Message-ID: <272c0f71-e817-44a6-8798-0a1535427ba9@redhat.com> (raw)
In-Reply-To: <20240410193150.655df790@p-imbrenda>
[...]
>> + if (rc == -E2BIG) {
>> + /*
>> + * Splitting might fail with -EBUSY due to unexpected folio
>> + * references, just like make_folio_secure(). So handle it
>> + * ahead of time without the PTL being held.
>> + */
>> + folio_lock(folio);
>> + rc = split_folio(folio);
>
> if split_folio returns -EAGAIN...
>
>> + folio_unlock(folio);
>> + folio_put(folio);
>> + }
>> +
>> if (rc == -EAGAIN) {
>
> ... we will not skip this ...
>
>> /*
>> * If we are here because the UVC returned busy or partial
>> * completion, this is just a useless check, but it is safe.
>> */
>> - wait_on_page_writeback(page);
>> - put_page(page);
>> + folio_wait_writeback(folio);
>> + folio_put(folio);
>
> ... and we will do one folio_put() too many
>
>> } else if (rc == -EBUSY) {
>> /*
>> * If we have tried a local drain and the page refcount
>
> are we sure that split_folio() can never return -EAGAIN now and in the
> future too?
Yes, and in contrast to documentation, that can actually happen! The
documentation is even wrong: we return -EAGAIN if there are unexpected
folio references (e.g., pinned), thanks for raising that.
>
> maybe just change it to } else if (... ?
I think I'll make it all clearer by handling split_folio() return values
separately.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-04-11 9:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 16:36 [PATCH v1 0/5] s390: page_mapcount(), page_has_private() and PG_arch_1 David Hildenbrand
2024-04-04 16:36 ` [PATCH v1 1/5] s390/uv: don't call wait_on_page_writeback() without a reference David Hildenbrand
2024-04-10 17:21 ` Claudio Imbrenda
2024-04-11 8:24 ` David Hildenbrand
2024-04-11 13:13 ` Alexander Gordeev
2024-04-04 16:36 ` [PATCH v1 2/5] s390/uv: convert gmap_make_secure() to work on folios David Hildenbrand
2024-04-05 3:29 ` Matthew Wilcox
[not found] ` <67557c5b-afd8-4578-a00d-6750accc1026@redhat.com>
2024-04-10 17:32 ` Claudio Imbrenda
2024-04-10 17:31 ` Claudio Imbrenda
2024-04-11 9:09 ` David Hildenbrand [this message]
2024-04-04 16:36 ` [PATCH v1 3/5] s390/uv: convert PG_arch_1 users to only work on small folios David Hildenbrand
2024-04-05 3:36 ` Matthew Wilcox
2024-04-10 17:42 ` Claudio Imbrenda
2024-04-04 16:36 ` [PATCH v1 4/5] s390/uv: update PG_arch_1 comment David Hildenbrand
2024-04-10 17:19 ` Claudio Imbrenda
2024-04-04 16:36 ` [PATCH v1 5/5] s390/hugetlb: convert PG_arch_1 code to work on folio->flags David Hildenbrand
2024-04-05 3:42 ` [PATCH v1 0/5] s390: page_mapcount(), page_has_private() and PG_arch_1 Matthew Wilcox
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=272c0f71-e817-44a6-8798-0a1535427ba9@redhat.com \
--to=david@redhat.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.com \
--cc=thuth@redhat.com \
--cc=willy@infradead.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