Received: by 10.192.165.156 with SMTP id m28csp1128772imm; Wed, 11 Apr 2018 13:00:02 -0700 (PDT) X-Google-Smtp-Source: AIpwx49QNzFclARfSkA73FKP3dph5dWNum8j0PVn6ua784uAcurGFEkDiVI2L6GjFowyu/wnXA6G X-Received: by 10.98.163.68 with SMTP id s65mr5177068pfe.13.1523476802907; Wed, 11 Apr 2018 13:00:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523476802; cv=none; d=google.com; s=arc-20160816; b=P/uv297J6ZVyFV0Vbu0MwkqCWH3MJUSyqSgF+/tlcI0EvNsW212uo05Nsai8iwllui 9xdE+tuF4ItmS116vXoZnZgy13f8m2Vyvu8weBRK7//qeON1GrWJMYUz5aWwQmiskvNJ PcG4E1sh4RBM1EqiWsMwbpO8OAUUWHt8Dt+gCwWdTViBk2TFqcQbQsYygp565nhHLHwZ hC0SSC3H/8przes11UMk4UnMB606QXclynuvS2Ssn4Vb9M1EZpDm/sNya9wctyB4tyFd 3d93+fUA2LIypVq9s35LzBUVOFlGxHwvfYqBVxliOYHNCibqSe9uzBrEZBFbRtvjms7c xPXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=FPpPRgCjSq/SDeQCy8WK/rfpshgdGdW2d/xZVGnm5p0=; b=XKxmzL3URj2yelqDizuJ+ZtrI+EvkrwZ6e1X8gnzvyVg8s+MmzvHRzfBGt9D+BYAq7 IKaiNR4uUfAeGvfjPovRLYI3JpWP2k1F00yp5wj96UBG1yOz362nh9ax68cv/DOiaVAn h0IkdwaOiomAbNK7vR4mB9Zhl6ZCO60EuO+QR19VI3Vir05IUsp0dY5gRcLjhSV3rXir jj8pT74hXZ0dK41CbAVTPz17yvMY10SGwgFFJJsFHa9jlPuocAFBQnBW4CDcNj35KrC3 Qne59iDzr2HMWGaQ4DB9TDeoP7HMWUfpvwrcTTzRZ2VhWhs7KqkS2su8LjFRCA2L+0+u lKTQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f34-v6si1661161plf.362.2018.04.11.12.59.25; Wed, 11 Apr 2018 13:00:02 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756367AbeDKS5O (ORCPT + 99 others); Wed, 11 Apr 2018 14:57:14 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:36198 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756354AbeDKS5K (ORCPT ); Wed, 11 Apr 2018 14:57:10 -0400 Received: from localhost (LFbn-1-12247-202.w90-92.abo.wanadoo.fr [90.92.61.202]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id 23343C06; Wed, 11 Apr 2018 18:57:09 +0000 (UTC) From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Vignesh R , Sasha Levin Subject: [PATCH 4.9 070/310] serial: 8250: omap: Disable DMA for console UART Date: Wed, 11 Apr 2018 20:33:29 +0200 Message-Id: <20180411183625.327950621@linuxfoundation.org> X-Mailer: git-send-email 2.17.0 In-Reply-To: <20180411183622.305902791@linuxfoundation.org> References: <20180411183622.305902791@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.9-stable review patch. If anyone has any objections, please let me know. ------------------ From: Vignesh R [ Upstream commit 84b40e3b57eef1417479c00490dd4c9f6e5ffdbc ] Kernel always writes log messages to console via serial8250_console_write()->serial8250_console_putchar() which directly accesses UART_TX register _without_ using DMA. But, if other processes like systemd using same UART port, then these writes are handled by a different code flow using 8250_omap driver where there is provision to use DMA. It seems that it is possible that both DMA and CPU might simultaneously put data to UART FIFO and lead to potential loss of data due to FIFO overflow and weird data corruption. This happens when both kernel console and userspace tries to write simultaneously to the same UART port. Therefore, disable DMA on kernel console port to avoid potential race between CPU and DMA. Signed-off-by: Vignesh R Signed-off-by: Greg Kroah-Hartman Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman --- drivers/tty/serial/8250/8250_omap.c | 4 ++++ 1 file changed, 4 insertions(+) --- a/drivers/tty/serial/8250/8250_omap.c +++ b/drivers/tty/serial/8250/8250_omap.c @@ -613,6 +613,10 @@ static int omap_8250_startup(struct uart up->lsr_saved_flags = 0; up->msr_saved_flags = 0; + /* Disable DMA for console UART */ + if (uart_console(port)) + up->dma = NULL; + if (up->dma) { ret = serial8250_request_dma(up); if (ret) {