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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 16 Mar 2012 19:46:28 +0900
From:	"Shimoda, Yoshihiro" <>
To:	David Miller <>
Subject: Re: [PATCH 5/5] net: sh_eth: use NAPI

2012/03/16 18:15, David Miller wrote:
> From: "Shimoda, Yoshihiro" <>
> Date: Fri, 16 Mar 2012 17:46:18 +0900
> sh_eth_interrupt takes mdp->lock, and:
>> +static int sh_eth_poll(struct napi_struct *napi, int budget)
>> +{
>> +	struct sh_eth_private *mdp = container_of(napi, struct sh_eth_private,
>> +						  napi);
>> +	struct net_device *ndev = mdp->ndev;
>> +	struct sh_eth_cpu_data *cd = mdp->cd;
>> +	int work_done = 0, txfree_num;
>> +	u32 intr_status = sh_eth_read(ndev, EESR);
>> +
>> +	spin_lock(&mdp->lock);
> sh_eth_poll() runs from software interrupt context, therefore
> this can deadlock.

Thank you for the point. I will fix it.

> Even though you turned off interrupts in sh_eth_interrupt to
> enable NAPI mode, this can still happen, interrupts can be
> stuck in the interrupt controller, another device can be on
> the same interrupt line, etc.  Therefore you must handle
> this properly.

I see. I wrote a comment below in sh_eth_interrupt, but this
is a wrong comment.

+			/* Disable all interrupts */
+			sh_eth_write(ndev, 0, EESIPR);

It only disable the interrupts of the controller's channel.
It doesn't disable other devices. So, I will fix the comment.

> I would suggest _NOT_ fixing this by taking the lock with interrupts
> disabled in sh_eth_poll(), that defeats the whole prupose of
> converting to NAPI and this would also require you to change back
> the dev_kfree_skb() to dev_kfree_skb_irq().

I understood it. I will fix it.

> Instead, do what other drivers do, make your interrupt handler run
> completely lockless and have a sophisticated quiescence sequence
> when you want to sync interrupts off and make sure no async contexts
> are still running in the interrupt handler.  See tg3.c for one
> example of this.

Thank you for your suggestion. I will see the tg3.c.

> I'm toss this entire patch series, it needs a lot more work.

I understood it. I wlll resubmit entire patch series after I fix the code.

Best regards,
Yoshihiro Shimoda
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists