netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: tingwei liu <tingw.liu@gmail.com>
Cc: netdev@vger.kernel.org, Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	davem@davemloft.net, Eric Dumazet <eric.dumazet@gmail.com>,
	Ben Hutchings <bhutchings@solarflare.com>,
	Linus Torvalds <linus971@gmail.com>
Subject: Re: [PATCH v2 1/1]core:Change a wrong explain about dev_get_by_name
Date: Mon, 25 Mar 2013 19:44:10 +0400	[thread overview]
Message-ID: <515070CA.2010701@cogentembedded.com> (raw)
In-Reply-To: <CA+qZnSTm8kdmrzQLc03Jyk81cBtEpCNHqsT1fFCQ_vstzYcOiw@mail.gmail.com>

Hello.

On 25-03-2013 8:10, tingwei liu wrote:

> From: Tingwei Liu <tingw.liu@gmail.com>
> Date: Mon, 25 Mar 2013 11:09:59 +0800
> Subject: [PATCH] Change a wrong explain about dev_get_by_name

> a long time ago by the  commit.

    Did you mean "before the commit"?

>   commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2
>   Author: Linus Torvalds <torvalds@ppc970.osdl.org>
>   Date:   Sat Apr 16 15:20:36 2005 -0700

>      Linux-2.6.12-rc2

>      Initial git repository build. I'm not bothering with the full history,
>      even though we have it. We can create a separate "historical" git
>      archive of that later if we want to, and in the meantime it's about
>      3.2GB when imported into git - space that would just make the early
>      git days unnecessarily complicated, when we don't have a lot of good
>      infrastructure for it.

>      Let it rip!

> When function "list_netdevice" get write lock "dev_base_lock" only
> disable soft interrupt. So dev_get_by_name get read lock
> "dev_base_lock", can not called on interrupt context.

> Signed-off-by: Tingwei Liu <tingw.liu@gmail.com>
> ---
> Changes from v1:
> - add change log
> - add the commnet
>
>   net/core/dev.c |    8 ++++----
>   1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/net/core/dev.c b/net/core/dev.c
> index d540ced..20c5c7c 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -700,10 +700,10 @@ EXPORT_SYMBOL(dev_get_by_name_rcu);
>   *     @name: name to find
>   *
>   *     Find an interface by name. This can be called from any
> - *     context and does its own locking. The returned handle has
> - *     the usage count incremented and the caller must use dev_put() to
> - *     release it when it is no longer needed. %NULL is returned if no
> - *     matching device is found.
> + *     context except hard irq context and does its own locking.
> + *     The returned handle has the usage count incremented and the
> + *     caller must use dev_put() to release it when it is no longer
> + *     needed. %NULL is returned if no matching device is found.

    It seems your patch has all the tabs replaced by spaces.

WBR, Sergei

  reply	other threads:[~2013-03-25 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25  4:10 [PATCH v2 1/1]core:Change a wrong explain about dev_get_by_name tingwei liu
2013-03-25 15:44 ` Sergei Shtylyov [this message]
2013-03-25 16:09   ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=515070CA.2010701@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linus971@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=tingw.liu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).