[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5665D2B7.3040409@imap.cc>
Date: Mon, 7 Dec 2015 19:40:55 +0100
From: Tilman Schmidt <tilman@...p.cc>
To: Paul Bolle <pebolle@...cali.nl>,
Peter Hurley <peter@...leysoftware.com>,
Sasha Levin <sasha.levin@...cle.com>
Cc: isdn@...ux-pingi.de, davem@...emloft.net,
gigaset307x-common@...ts.sourceforge.net,
LKML <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
syzkaller <syzkaller@...glegroups.com>
Subject: Re: gigaset: freeing an active object
Am 07.12.2015 um 13:25 schrieb Paul Bolle:
>>> Otherwise we'd still be freeing memory
>>> managed through reference counting.
>>
>> Now I#m confused. I thought by following Peter's suggestion to put the
>> kfree() in the release method we'd avoid just that.
>
> Apparently it does, because I can't trigger the WARNING we're discussing
> here with your patch applied.
Nice.
> I'll have to dive into this stuff again,
> because apparently my mental model of what's going on is incomplete at
> best.
I won't claim anything like completeness for mine.
> In the mean time you might want to turn your patch into something that
> can actually be applied (with or without my Sign-off or Ack; I don't
> care how it finds its way into the tree). Please add add
> Fixes: 2869b23e4b95 ("[PATCH] drivers/isdn/gigaset: new M101 driver (v2)")
Will do. (Not today, though.)
Regards,
Tilman
--
Tilman Schmidt E-Mail: tilman@...p.cc
Bonn, Germany
Nous, on a des fleurs et des bougies pour nous protéger.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists