netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: poma <pomidorabelisima@gmail.com>,
	netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
	Francois Romieu <romieu@fr.zoreil.com>,
	Mike Massonnet <m8t@gandi.net>,
	Benedikt Meurer <benedikt.meurer@unix-ag.uni-siegen.de>,
	Bernhard Walle <bernhard.walle@gmx.de>,
	Hendrik Scholz <hscholz@raisdorf.net>,
	Florian Rivoal <frivoal@xfce.org>
Subject: Re: [PATCH net 1/1] r8169: fix sleepable allocation during netdevice stats retrieval.
Date: Wed, 9 Sep 2015 17:55:11 +0200	[thread overview]
Message-ID: <20150909155511.GD19913@calimero.vinschen.de> (raw)
In-Reply-To: <20150909155404.GC19913@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 638 bytes --]

On Sep  9 17:54, Corinna Vinschen wrote:
> On Sep  9 17:24, poma wrote:
> > [PATCH net] r8169: Fix sleeping function called during get_stats64
> > http://marc.info/?l=linux-netdev&m=144180123410135&q=raw
> > - the noise is still present
> 
> Are you really sure?  The entire dma_alloc/dma_free stuff has been moved
> away.  There's no locking or sleeping involved different from what was
> there before my original patch when calling .ndo_get_stats64.
> 
> How would I be able to reproduce this on the command line?

It would also be interesting to see the "noise" as it looks after
applying the above patch...


Corinna

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-09-09 15:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 14:05 BUG: sleeping function called from invalid context at mm/page_alloc.c:3186 poma
2015-09-04 18:36 ` David Miller
2015-09-04 20:59   ` [PATCH net 1/1] r8169: fix sleepable allocation during netdevice stats retrieval Francois Romieu
2015-09-04 22:22     ` David Miller
2015-09-04 23:11       ` Francois Romieu
2015-09-04 23:15         ` David Miller
2015-09-06 10:19     ` Corinna Vinschen
2015-09-06 20:20       ` Francois Romieu
2015-09-07  7:13       ` poma
2015-09-07  8:50         ` Corinna Vinschen
2015-09-07 14:43           ` poma
2015-09-08  6:36             ` poma
2015-09-09 15:24               ` poma
2015-09-09 15:54                 ` Corinna Vinschen
2015-09-09 15:55                   ` Corinna Vinschen [this message]
2015-09-09 18:34                     ` poma
2015-09-09 19:04                       ` David Miller
2015-09-10  0:38                         ` poma
2015-09-09 19:08                       ` Corinna Vinschen
2015-09-09 23:11                         ` poma
2015-09-09 23:51                           ` poma
2015-09-10  8:47                             ` Corinna Vinschen
2015-09-10 12:36                               ` poma
2015-09-10 14:29                                 ` Corinna Vinschen

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=20150909155511.GD19913@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=benedikt.meurer@unix-ag.uni-siegen.de \
    --cc=bernhard.walle@gmx.de \
    --cc=davem@davemloft.net \
    --cc=frivoal@xfce.org \
    --cc=hscholz@raisdorf.net \
    --cc=m8t@gandi.net \
    --cc=netdev@vger.kernel.org \
    --cc=pomidorabelisima@gmail.com \
    --cc=romieu@fr.zoreil.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).