linux-kernel - Re: [PATCH] Fix bug where kfree is called twice.

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20120426115459.GE6447@mwanda>
Date:	Thu, 26 Apr 2012 14:54:59 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	Rupesh Gujare <rgujare@...odevices.com>
Cc:	devel@...verdev.osuosl.org, gregkh@...uxfoundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix bug where kfree is called twice.

On Thu, Apr 26, 2012 at 09:44:16AM +0100, Rupesh Gujare wrote:
> Hi Dan,
> >It's a good patch and it fixes a bug, but could you resend with
> >the subject:
> >
> >[PATCH] Staging: ozwpan: Fix bug where kfree is called twice.
> Sorry about subject line. I should have spend a bit more time in
> formatting subject line.
> However it looks like Greg have already pulled this patch in
> staging-next branch.
> (Thanks Greg, for modifying subject line. I will be more careful next time.)
> 
> However, I will be happy if you still want me to resend this patch
> with correct subject line.
> 

Obviously don't resend.  *eyeroll*  I'll never ask you to resend
stuff just because I'm on a power trip.

> >We don't like to put a lot of bureaucracy infront of people
> >submitting actual bugfixes.  But you guys are the new maintainers
> >and you're going to need to know all this stuff eventually.  Also
> >could you give us a hint how likely the users are to hit this?
> >Should this go into 3.4 or only 3.5?
> I would have loved to get this patch in 3.4 as I am observing
> occasional crashes.
> However looks like Greg have queued it up for 3.5.

Everything goes into linux-next first.  That should have been put
in the changelog.  "We are seeing occasional crashes under load" or
whatever...  It's Greg's call and all, but generally it can't hurt
to ask nicely if you want stuff merged it into 3.4 as well.  ;)

regards,
dan carpenter

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/