From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756192Ab1IAIKp (ORCPT ); Thu, 1 Sep 2011 04:10:45 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:34502 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756018Ab1IAIKk convert rfc822-to-8bit (ORCPT ); Thu, 1 Sep 2011 04:10:40 -0400 Date: Thu, 1 Sep 2011 09:09:30 +0100 From: Alan Cox To: Geert Uytterhoeven Cc: WANG Cong , linux-kernel@vger.kernel.org, akpm@linux-foundation.org, Mikael Starvik , Jesper Nilsson , Alan Cox , linux-cris-kernel@axis.com, linux-serial@vger.kernel.org Subject: Re: [PATCH] cris: lower the printk level in cris serial driver Message-ID: <20110901090930.064c2775@lxorguk.ukuu.org.uk> In-Reply-To: References: <1314857640-6623-1-git-send-email-xiyou.wangcong@gmail.com> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.4; x86_64-redhat-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWysKsSBQMIAwIZCwj///8wIhxoRDXH9QHCAAABeUlEQVQ4jaXTvW7DIBAAYCQTzz2hdq+rdg494ZmBeE5KYHZjm/d/hJ6NfzBJpp5kRb5PHJwvMPMk2L9As5Y9AmYRBL+HAyJKeOU5aHRhsAAvORQ+UEgAvgddj/lwAXndw2laEDqA4x6KEBhjYRCg9tBFCOuJFxg2OKegbWjbsRTk8PPhKPD7HcRxB7cqhgBRp9Dcqs+B8v4CQvFdqeot3Kov6hBUn0AJitrzY+sgUuiA8i0r7+B3AfqKcN6t8M6HtqQ+AOoELCikgQSbgabKaJW3kn5lBs47JSGDhhLKDUh1UMipwwinMYPTBuIBjEclSaGZUk9hDlTb5sUTYN2SFFQuPe4Gox1X0FZOufjgBiV1Vls7b+GvK3SU4wfmcGo9rPPQzgIabfj4TYQo15k3bTHX9RIw/kniir5YbtJF4jkFG+dsDK1IgE413zAthU/vR2HVMmFUPIHTvF6jWCpFaGw/A3qWgnbxpSm9MSmY5b3pM1gvNc/gQfwBsGwF0VCtxZgAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > >        if (info->recv_cnt + recvl > 65536) { > > -               printk(KERN_CRIT > > +               printk(KERN_INFO > >                       "%s: Too much pending incoming serial data! Dropping %u bytes.\n", __func__, recvl); > >                return 0; > >        } > > I think dropped data warrants KERN_WARN. If you have an overflow you want to push the relevant tty flag into the queue. I'm not sure a printk is that useful - end users of embedded devices (or even PC desktops) won't see it anyway and if you have serial console it can actually make things worse Plus of course it's not rate limited here so its a log wiping vector ...