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] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 3 Oct 2013 11:16:52 -0700
From:	Andi Kleen <ak@...ux.intel.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	eranian@...gle.com
Subject: Re: [PATCH 11/11] perf: Avoid uninitialized sample type reference in
 __perf_event__output_id_sample

> Forcing multiple, unnecessary rounds of emails instead of clearly 
> volunteering all technical information that is related to the matter is 
> something Andi is still doing routinely.

Sorry all the information was in the full email thread
(including the intro). And the patch description 
clearly described the problem in your code.

As the patches spanned many subsystems you were only copied
on the patches that affect your subsystem, and not on
the intro (as git send-email doesn't seem to support that)

Here are possible alternatives. Please let me know which ones
you prefer and I'll try to adapt to your specific preferences
in the future:

[ ] Always copy you guys on all patches of 
subsystem spanning patch kits that are mostly of no relevance
to you. 

[ ] Repeat the complete intro in every patch.

[ ] You think uninitialized are not a problem and you
don't want to see any patches related to that.

[ ] You are not interested in fixing static checker problems in your
subsystem and don't want to see any patches related to that.

Thanks.

-Andi
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ