All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Martin Peres <martin.peres@linux.intel.com>
Cc: intel-gfx-trybot@lists.freedesktop.org,
	Alexander Usyskin <alexander.usyskin@intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] mei: discard messages from not connected client during power down.
Date: Tue, 29 May 2018 11:04:07 +0200	[thread overview]
Message-ID: <20180529090407.GA9530@kroah.com> (raw)
In-Reply-To: <20180529085616.29820-1-martin.peres@linux.intel.com>

On Tue, May 29, 2018 at 11:56:16AM +0300, Martin Peres wrote:
> From: Alexander Usyskin <alexander.usyskin@intel.com>
> 
> This fixes regression introduced by
> commit 8d52af6795c0 ("mei: speed up the power down flow")
> 
> In power down or suspend flow a message can still be received
> from the FW because the clients fake disconnection.
> In normal case we interpret messages w/o destination as corrupted
> and link reset is performed in order to clean the channel,
> but during power down link reset is already in progress resulting
> in endless loop. To resolve the issue under power down flow we
> discard messages silently.
> 
> Cc: <stable@vger.kernel.org> 4.16+
> Fixes: 8d52af6795c0 ("mei: speed up the power down flow")
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=199541
> Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> ---
>  drivers/misc/mei/interrupt.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)

Shouldn't this patch go through the char/misc maintainer?

confused,

greg k-h

  reply	other threads:[~2018-05-29  9:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29  8:56 [PATCH] mei: discard messages from not connected client during power down Martin Peres
2018-05-29  9:04 ` Greg KH [this message]
2018-05-29 10:16   ` Martin Peres

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=20180529090407.GA9530@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.usyskin@intel.com \
    --cc=intel-gfx-trybot@lists.freedesktop.org \
    --cc=martin.peres@linux.intel.com \
    --cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.