netdev - Re: [RFC PATCH] net/core: support runtime PM on net

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CACVXFVOJVVe+PGVBeBaHA1XcJ2s5p3jeqg6=3-6c3ouH70xG0A@mail.gmail.com>
Date:	Wed, 17 Oct 2012 22:17:48 +0800
From:	Ming Lei <ming.lei@...onical.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	"David S. Miller" <davem@...emloft.net>,
	Oliver Neukum <oneukum@...e.de>,
	Alan Stern <stern@...land.harvard.edu>, netdev@...r.kernel.org,
	linux-pm@...r.kernel.org
Subject: Re: [RFC PATCH] net/core: support runtime PM on net_device

On Wed, Oct 17, 2012 at 1:07 AM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> On Wednesday 10 of October 2012 20:58:33 Ming Lei wrote:
>> In ioctl path on net_device, the physical deivce is often
>> touched, but the physical device may have been put into runtime
>> suspend state already, so cause some utilitis(ifconfig, ethtool,
>> ...) to return failure in this situation.
>>
>> This patch enables runtime PM on net_device and mark it as
>> no_callbacks, and resumes the net_device if physical device
>> is to be accessed, then suspends it after completion of the
>> access.
>>
>> This patch fixes the problem above.
>>
>> Signed-off-by: Ming Lei <ming.lei@...onical.com>
>
> Well, it looks good in principle.
>
> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>

OK, I will prepare -v1 for merge later if no one has objection on
the patch, which has a compile error.('ret' is not defined in
dev_ethtool)

Thanks,
--
Ming Lei
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html