From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: David Vrabel <david.vrabel@citrix.com>,
xen-devel@lists.xen.org, linux-kernel@vger.kernel.org,
linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 4/5] xen-fbfront: handle backend CLOSED without CLOSING
Date: Tue, 23 Oct 2012 04:50:44 +0000 [thread overview]
Message-ID: <50862224.60908@gmx.de> (raw)
In-Reply-To: <20121019130011.GD26830@phenom.dumpdata.com>
Hi Konrad,
On 10/19/2012 01:00 PM, Konrad Rzeszutek Wilk wrote:
> On Thu, Oct 18, 2012 at 11:03:37AM +0100, David Vrabel wrote:
>> From: David Vrabel <david.vrabel@citrix.com>
>>
>> Backend drivers shouldn't transistion to CLOSED unless the frontend is
>> CLOSED. If a backend does transition to CLOSED too soon then the
>> frontend may not see the CLOSING state and will not properly shutdown.
>>
>> So, treat an unexpected backend CLOSED state the same as CLOSING.
>>
>> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
>> Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>> ---
>> Cc: linux-fbdev@vger.kernel.org
>> Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
>
> Hey Florian,
>
> Should I prep a git pull for you with this or would it be OK
> if I just have your Ack to put this in my git pull for Linus?
Feel free to take it and add
Acked-by: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Best regards,
Florian Tobias Schandinat
>
> Thanks!
>> ---
>> drivers/video/xen-fbfront.c | 5 ++++-
>> 1 files changed, 4 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/video/xen-fbfront.c b/drivers/video/xen-fbfront.c
>> index b7f5173..917bb56 100644
>> --- a/drivers/video/xen-fbfront.c
>> +++ b/drivers/video/xen-fbfront.c
>> @@ -641,7 +641,6 @@ static void xenfb_backend_changed(struct xenbus_device *dev,
>> case XenbusStateReconfiguring:
>> case XenbusStateReconfigured:
>> case XenbusStateUnknown:
>> - case XenbusStateClosed:
>> break;
>>
>> case XenbusStateInitWait:
>> @@ -670,6 +669,10 @@ InitWait:
>> info->feature_resize = val;
>> break;
>>
>> + case XenbusStateClosed:
>> + if (dev->state = XenbusStateClosed)
>> + break;
>> + /* Missed the backend's CLOSING state -- fallthrough */
>> case XenbusStateClosing:
>> xenbus_frontend_closed(dev);
>> break;
>> --
>> 1.7.2.5
>
prev parent reply other threads:[~2012-10-23 4:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 10:02 [PATCH 0/5] drivers: xen frontend devices should handle missed backend CLOSING David Vrabel
2012-10-18 10:03 ` [PATCH 4/5] xen-fbfront: handle backend CLOSED without CLOSING David Vrabel
2012-10-19 13:00 ` Konrad Rzeszutek Wilk
2012-10-23 4:50 ` Florian Tobias Schandinat [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=50862224.60908@gmx.de \
--to=florianschandinat@gmx.de \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).