All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	linux-serial@vger.kernel.org, linux-omap@vger.kernel.org,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: 8250: 8250_omap: Fix possible interrupt storm
Date: Thu, 13 May 2021 16:17:20 +0200	[thread overview]
Message-ID: <YJ008MjjewRUTn9Z@kroah.com> (raw)
In-Reply-To: <20210511151955.28071-1-vigneshr@ti.com>

On Tue, May 11, 2021 at 08:49:55PM +0530, Vignesh Raghavendra wrote:
> It is possible that RX TIMEOUT is signalled after RX FIFO has been
> drained, in which case a dummy read of RX FIFO is required to clear RX
> TIMEOUT condition. Otherwise, RX TIMEOUT condition is not cleared
> leading to an interrupt storm
> 
> Cc: stable@vger.kernel.org

How far back does this need to go?  What commit id does this fix?  What
caused this to just show up now vs. previously?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	linux-serial@vger.kernel.org, linux-omap@vger.kernel.org,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: 8250: 8250_omap: Fix possible interrupt storm
Date: Thu, 13 May 2021 16:17:20 +0200	[thread overview]
Message-ID: <YJ008MjjewRUTn9Z@kroah.com> (raw)
In-Reply-To: <20210511151955.28071-1-vigneshr@ti.com>

On Tue, May 11, 2021 at 08:49:55PM +0530, Vignesh Raghavendra wrote:
> It is possible that RX TIMEOUT is signalled after RX FIFO has been
> drained, in which case a dummy read of RX FIFO is required to clear RX
> TIMEOUT condition. Otherwise, RX TIMEOUT condition is not cleared
> leading to an interrupt storm
> 
> Cc: stable@vger.kernel.org

How far back does this need to go?  What commit id does this fix?  What
caused this to just show up now vs. previously?

thanks,

greg k-h

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-05-13 14:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11 15:19 [PATCH] serial: 8250: 8250_omap: Fix possible interrupt storm Vignesh Raghavendra
2021-05-11 15:19 ` Vignesh Raghavendra
2021-05-13 14:17 ` Greg Kroah-Hartman [this message]
2021-05-13 14:17   ` Greg Kroah-Hartman
2021-05-28  5:39   ` Tony Lindgren
2021-05-28  5:39     ` Tony Lindgren
2021-05-28  6:11     ` Vignesh Raghavendra
2021-05-28  6:11       ` Vignesh Raghavendra
2021-05-28  9:00       ` Greg Kroah-Hartman
2021-05-28  9:00         ` Greg Kroah-Hartman
2021-06-22  6:15       ` Jan Kiszka
2021-06-22  6:15         ` Jan Kiszka
2021-06-22  6:23         ` Vignesh Raghavendra
2021-06-22  6:23           ` Vignesh Raghavendra
2021-07-12 20:27           ` andy
2021-07-13  8:54             ` Vignesh Raghavendra
2021-07-13  8:54               ` Vignesh Raghavendra
2021-07-13  9:09               ` Andy Shevchenko
2021-07-13  9:09                 ` Andy Shevchenko
2021-07-13  9:13               ` Andy Shevchenko
2021-07-13  9:13                 ` Andy Shevchenko
2021-07-27 10:39                 ` Tony Lindgren
2021-07-27 10:39                   ` Tony Lindgren

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=YJ008MjjewRUTn9Z@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jan.kiszka@siemens.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=vigneshr@ti.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 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.