From: Peter Maydell <peter.maydell@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
luigi burdo <intermediadc@hotmail.com>,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] memory: fix flatview_access_valid RCU read lock/unlock imbalance
Date: Fri, 9 Mar 2018 16:42:12 +0000 [thread overview]
Message-ID: <CAFEAcA8zOUcL0yiOPBU+t8zJ2PanJ8HbqLfi9QoB+7uCkwJZZg@mail.gmail.com> (raw)
In-Reply-To: <096e970e-87f0-9aee-63a9-6d0194147b71@redhat.com>
On 7 March 2018 at 13:29, Thomas Huth <thuth@redhat.com> wrote:
> On 07.03.2018 14:02, Paolo Bonzini wrote:
>> Fixes: 11e732a5ed46903f997985bed4c3767ca28a7eb6
>> Reported-by: Cornelia Huck <cohuck@redhat.com>
>> Reported-by: luigi burdo <intermediadc@hotmail.com>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> exec.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/exec.c b/exec.c
>> index 604f03c535..a9181e6417 100644
>> --- a/exec.c
>> +++ b/exec.c
>> @@ -3393,7 +3393,6 @@ static bool flatview_access_valid(FlatView *fv, hwaddr addr, int len,
>> if (!memory_access_is_direct(mr, is_write)) {
>> l = memory_access_size(mr, l, addr);
>> if (!memory_region_access_valid(mr, xlat, l, is_write)) {
>> - rcu_read_unlock();
>> return false;
>> }
>> }
>>
>
> Thanks, this seems to fix the problem with the sam640ex and 40p machines.
>
> Tested-by: Thomas Huth <thuth@redhat.com>
Thanks, applied to master since I ran into this too.
-- PMM
prev parent reply other threads:[~2018-03-09 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 13:02 [Qemu-devel] [PATCH] memory: fix flatview_access_valid RCU read lock/unlock imbalance Paolo Bonzini
2018-03-07 13:23 ` Cornelia Huck
2018-03-07 13:29 ` Thomas Huth
2018-03-09 16:42 ` Peter Maydell [this message]
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=CAFEAcA8zOUcL0yiOPBU+t8zJ2PanJ8HbqLfi9QoB+7uCkwJZZg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=cohuck@redhat.com \
--cc=intermediadc@hotmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).