linux-kernel - Re: [PATCHv2 3/4] dw_dmac: change {dev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1350481018.3568.3.camel@smile>
Date:	Wed, 17 Oct 2012 16:36:58 +0300
From:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:	balbi@...com
Cc:	Viresh Kumar <viresh.linux@...il.com>,
	Vinod Koul <vinod.koul@...el.com>,
	linux-kernel@...r.kernel.org, spear-devel <spear-devel@...t.st.com>
Subject: Re: [PATCHv2 3/4] dw_dmac: change {dev_}printk() to corresponding
 macros

On Wed, 2012-10-17 at 16:09 +0300, Felipe Balbi wrote: 
> Hi,
> 
> On Wed, Oct 17, 2012 at 01:31:17PM +0300, Andy Shevchenko wrote:
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
> > ---
> >  drivers/dma/dw_dmac.c |   15 ++++++---------
> >  1 file changed, 6 insertions(+), 9 deletions(-)
> > 
> > diff --git a/drivers/dma/dw_dmac.c b/drivers/dma/dw_dmac.c
> > index c27c125..60b172a 100644
> > --- a/drivers/dma/dw_dmac.c
> > +++ b/drivers/dma/dw_dmac.c
> > @@ -456,9 +456,8 @@ static void dwc_scan_descriptors(struct dw_dma *dw, struct dw_dma_chan *dwc)
> >  
> >  static inline void dwc_dump_lli(struct dw_dma_chan *dwc, struct dw_lli *lli)
> >  {
> > -	dev_printk(KERN_CRIT, chan2dev(&dwc->chan),
> > -			"  desc: s0x%x d0x%x l0x%x c0x%x:%x\n",
> > -			lli->sar, lli->dar, lli->llp, lli->ctlhi, lli->ctllo);
> > +	dev_crit(chan2dev(&dwc->chan), "  desc: s0x%x d0x%x l0x%x c0x%x:%x\n",
> > +		 lli->sar, lli->dar, lli->llp, lli->ctlhi, lli->ctllo);
> 
> is this really critical ? To me it looks more like a debugging message.
This one is used in two cases, where one is marked as "error", another -
"critical"

> 
> >  }
> >  
> >  static void dwc_handle_error(struct dw_dma *dw, struct dw_dma_chan *dwc)
> > @@ -492,10 +491,8 @@ static void dwc_handle_error(struct dw_dma *dw, struct dw_dma_chan *dwc)
> >  	 * controller flagged an error instead of scribbling over
> >  	 * random memory locations.
> >  	 */
> > -	dev_printk(KERN_CRIT, chan2dev(&dwc->chan),
> > -			"Bad descriptor submitted for DMA!\n");
> > -	dev_printk(KERN_CRIT, chan2dev(&dwc->chan),
> > -			"  cookie: %d\n", bad_desc->txd.cookie);
> > +	dev_crit(chan2dev(&dwc->chan), "Bad descriptor submitted for DMA!\n");
> > +	dev_crit(chan2dev(&dwc->chan), "  cookie: %d\n", bad_desc->txd.cookie);
> 
> now this is critical, indeed. I would suggest using dev_WARN_ONCE() so
> that it's noisy enough to catch the failing user.
To this and upper comment, there is an explanation why it's critical. I
guess the WARN_ONCE is not good enough, for example if we have more than
one user making such noise.

> 
> >  	dwc_dump_lli(dwc, &bad_desc->lli);
> >  	list_for_each_entry(child, &bad_desc->tx_list, desc_node)
> >  		dwc_dump_lli(dwc, &child->lli);
> > @@ -1625,8 +1622,8 @@ static int __devinit dw_probe(struct platform_device *pdev)
> >  
> >  	dma_writel(dw, CFG, DW_CFG_DMA_EN);
> >  
> > -	printk(KERN_INFO "%s: DesignWare DMA Controller, %d channels\n",
> > -			dev_name(&pdev->dev), nr_channels);
> > +	pr_info("%s: DesignWare DMA Controller, %d channels\n",
> > +		dev_name(&pdev->dev), nr_channels);
> 
> you have a struct device available in platform_device, please use
> dev_info() or dev_dbg().
Agreed.


-- 
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/