netdev - Re: Pull request: bluetooth-2.6 2010-07-08

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1278631734.10421.88.camel@localhost.localdomain>
Date:	Thu, 08 Jul 2010 20:28:54 -0300
From:	Marcel Holtmann <marcel@...tmann.org>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org
Subject: Re: Pull request: bluetooth-2.6 2010-07-08

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


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html