From: Marcel Holtmann <marcel@holtmann.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: Pull request: bluetooth-2.6 2010-07-08
Date: Thu, 08 Jul 2010 20:28:54 -0300 [thread overview]
Message-ID: <1278631734.10421.88.camel@localhost.localdomain> (raw)
In-Reply-To: <20100708.154637.71104736.davem@davemloft.net>
Hi Dave,
> > these patches fix a few bugs and crashes and also two security related
> > issues with the authentication procedure.
>
> 13 changes is too much this late in the -RC series. Fixes need to
> trickle in, in small quantities, and therefore it's critical that
> maintainers submit fixes often and as soon as they are ready.
>
> Please pick a small number of the most critical fixes, say 3 or 4. An
> easy way to roughly quantify which ones shoule be included is:
>
> 1) Is there an OOPS or crash regression reported by real users and
> listed in the official lkml regression list which is caused by this
> problem?
>
> 2) Is there an exploitable security concern fixed by this change?
>
> Else, it's only net-next-2.6 material.
>
> For example:
>
> Bluetooth: Remove max_tx and tx_window module paramenters from L2CAP
>
> Things like that change are absolutely not appropriate at this
> stage in the post merge-window development environment.
I can take these out and leave them for -next. That is fine with me, but
you asked Gustavo to remove these. And so I left them in.
Regards
Marcel
next prev parent reply other threads:[~2010-07-08 23:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 19:59 Pull request: bluetooth-2.6 2010-07-08 Marcel Holtmann
2010-07-08 19:59 ` [PATCH 01/13] Bluetooth: Remove max_tx and tx_window module paramenters from L2CAP Marcel Holtmann
2010-07-08 19:59 ` [PATCH 02/13] Bluetooth: Remove L2CAP Extended Features from Kconfig Marcel Holtmann
2010-07-08 19:59 ` [PATCH 03/13] Bluetooth: Fix drop of packets with invalid req_seq/tx_seq Marcel Holtmann
2010-07-08 19:59 ` [PATCH 04/13] Bluetooth: Fix bug with ERTM vars increment Marcel Holtmann
2010-07-08 19:59 ` [PATCH 05/13] Bluetooth: Only check SAR bits if frame is an I-frame Marcel Holtmann
2010-07-08 19:59 ` [PATCH 06/13] Bluetooth: Fix bug in l2cap_ertm_send() behavior Marcel Holtmann
2010-07-08 19:59 ` [PATCH 07/13] Bluetooth: Fix SREJ_QUEUE corruption in L2CAP Marcel Holtmann
2010-07-08 19:59 ` [PATCH 08/13] Bluetooth: Fix bug with ERTM minimum packet length Marcel Holtmann
2010-07-08 19:59 ` [PATCH 09/13] Bluetooth: Proper shutdown ERTM when closing the channel Marcel Holtmann
2010-07-08 19:59 ` [PATCH 10/13] Bluetooth: Fix L2CAP control bit field corruption Marcel Holtmann
2010-07-08 20:00 ` [PATCH 11/13] Bluetooth: Check L2CAP pending status before sending connect request Marcel Holtmann
2010-07-08 20:00 ` [PATCH 12/13] Bluetooth: Reset the security level after an authentication failure Marcel Holtmann
2010-07-08 20:00 ` [PATCH 13/13] Bluetooth: Update sec_level/auth_type for already existing connections Marcel Holtmann
2010-07-08 22:46 ` Pull request: bluetooth-2.6 2010-07-08 David Miller
2010-07-08 23:28 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-08 23:40 Marcel Holtmann
2010-07-09 0:28 ` 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=1278631734.10421.88.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=davem@davemloft.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox