All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Khlebnikov <khlebnikov@openvz.org>
To: David Miller <davem@davemloft.net>
Cc: brouer@redhat.com, netdev@vger.kernel.org, edumazet@google.com,
	fw@strlen.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: frag, fix race conditions in LRU list maintenance
Date: Tue, 07 May 2013 09:22:27 +0400	[thread overview]
Message-ID: <51888F93.3030300@openvz.org> (raw)
In-Reply-To: <20130506.110800.1388239604905052651.davem@davemloft.net>

David Miller wrote:
> From: Jesper Dangaard Brouer<brouer@redhat.com>
> Date: Mon, 6 May 2013 09:33:18 +0200
>
>> This a good fix, and better than my earlier attempt at fixing this.
>   ...
>> Signed-off-by: Jesper Dangaard Brouer<brouer@redhat.com>
>
> Applied, but this patch was generated against a very old tree,
> one before the q->net->nqueues stuff was added.
>
> I sorted out the conflicts but someone needs to double-check
> my work.

All right. Sorry, my patch is against 3.9

Seems like this bug allows to crash kernel remotely.
Should I send it to stable@ for including into 3.9.y or
you already have a bunch of patches for it?

  reply	other threads:[~2013-05-07  5:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-05 14:56 [PATCH] net: frag, fix race conditions in LRU list maintenance Konstantin Khlebnikov
2013-05-05 17:36 ` David Miller
2013-05-05 18:30 ` Florian Westphal
2013-05-06  7:33 ` Jesper Dangaard Brouer
2013-05-06 15:08   ` David Miller
2013-05-07  5:22     ` Konstantin Khlebnikov [this message]
2013-05-07  9:13       ` David Miller
2013-05-08 15:32     ` Jesper Dangaard Brouer

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=51888F93.3030300@openvz.org \
    --to=khlebnikov@openvz.org \
    --cc=brouer@redhat.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.