netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: marcel@holtmann.org
Cc: torvalds@linux-foundation.org, netdev@vger.kernel.org
Subject: Re: Pull request: bluetooth-2.6 2010-03-21
Date: Sun, 21 Mar 2010 18:03:39 -0700 (PDT)	[thread overview]
Message-ID: <20100321.180339.57436668.davem@davemloft.net> (raw)
In-Reply-To: <cover.1269149354.git.marcel@holtmann.org>

From: Marcel Holtmann <marcel@holtmann.org>
Date: Sun, 21 Mar 2010 06:41:34 +0100

> these patches fix a potential remote denial of service in the L2CAP
> layer and a potential bad memory access with some sysfs files.

I've pulled this in thanks Marcel.

      parent reply	other threads:[~2010-03-22  1:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-21  5:41 Pull request: bluetooth-2.6 2010-03-21 Marcel Holtmann
2010-03-21  5:41 ` [PATCH 1/3] Bluetooth: Fix potential bad memory access with sysfs files Marcel Holtmann
2010-03-21  5:41   ` [PATCH 2/3] Bluetooth: Convert debug files to actually use debugfs instead of sysfs Marcel Holtmann
2010-03-21  5:41     ` [PATCH 3/3] Bluetooth: Fix kernel crash on L2CAP stress tests Marcel Holtmann
2010-03-22  1:03 ` David Miller [this message]

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=20100321.180339.57436668.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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).