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: <49F5C305.60807@linux.intel.com>
Date:	Mon, 27 Apr 2009 16:36:53 +0200
From:	Andi Kleen <ak@...ux.intel.com>
To:	Steven Rostedt <rostedt@...dmis.org>
CC:	Huang Ying <ying.huang@...el.com>,
	Robert Richter <robert.richter@....com>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>
Subject: Patenting kernel patches was Re: Re-implement MCE log ring buffer
 as per-CPU ring buffer


>>> I've put in for a patent application on the algorithm so I must wait till 
>>> it is processed before I can release the code.
>> When will it be merged by mainline kernel? Do you have a plan?
>>
>> We do have some scalability issues of current mcelog implementation, and
>> hopes that can be solved as soon as possible, perhaps for 2.6.31?
> 
> Yes, I plan on being able to post it before the 31 merge window opens. 
> I'll ping the lawyer to expedite the process.

Sorry, but this is quite ridiculous. Are you serious?

Why would we want such a patented algorithm in the kernel? Normally the standard
policy is to avoid patented algorithms (unless there's really no alternative like
with RCU which is clearly not the case here) and I'm not aware of this policy haven't
changed.

And also holding up perfectly good uncontaminated patches for something
patented seems especially wrong.

I think we should move forward with a standard non patented ring
buffer Ying was working on for this and avoid the patent mess as
far as possible.

-Andi (who wonders if he isn't in bizarro land now)

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