Hi Johan,
On Wed, Oct 08, 2014 at 11:37:06AM +0300, Johan Hedberg wrote:
> Hi Alex,
>
> On Wed, Oct 08, 2014, Alexander Aring wrote:
> > This patch reverts commit:
> >
> > a7807d73 ("Bluetooth: 6lowpan: Avoid memory leak if memory allocation
> > fails")
> >
> > which was wrong suggested by Alexander Aring. The function skb_unshare
> > run also kfree_skb on failure.
> >
> > Signed-off-by: Alexander Aring <alex.aring@xxxxxxxxx>
> > ---
> > compile tested only.
> >
> > net/bluetooth/6lowpan.c | 8 ++------
> > 1 file changed, 2 insertions(+), 6 deletions(-)
>
> This doesn't look like something that should only go to bluetooth-next
> (which you've tagged it for). The bluetooth-next tree (since 3.17 has
> been released) has moved to catering 3.19 patches whereas this patch
> seems to be something that's fixing an issue heading to 3.18-rc1. So it
> seems to me this patch should in fact be going to the bluetooth.git tree
> instead of bluetooth-next.git. Am I right?
>
yes, but commit a7807d73 isn't inside of bluetooth.git right now. Should
I rebase it to some other repository or cc stable here?
- Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
