| 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
| ||
|
Message-ID: <4F5F4C86.5050501@windriver.com> Date: Tue, 13 Mar 2012 09:32:54 -0400 From: Paul Gortmaker <paul.gortmaker@...driver.com> To: Olaf Hering <olaf@...fle.de> CC: <stable@...nel.org>, <linux-kernel@...r.kernel.org>, <stable-review@...nel.org>, Greg Kroah-Hartman <gregkh@...e.de> Subject: Re: [34-longterm 020/196] staging: hv: use sync_bitops when interacting with the hypervisor On 12-03-13 03:00 AM, Olaf Hering wrote: > On Mon, Mar 12, Paul Gortmaker wrote: > >> From: Olaf Hering <olaf@...fle.de> >> >> ------------------- >> This is a commit scheduled for the next v2.6.34 longterm release. >> If you see a problem with using this for longterm, please comment. >> ------------------- >> >> commit 22356585712d1ff08fbfed152edd8b386873b238 upstream. > > Unless there is a happy user of the hv drivers in this old kernel, it > makes no sense to backport just this one patch. There is no real way any of can tell just exactly who is using what feature in what release. > > I suggest to leave drivers/staging/hv alone in longterm releases, or > backport the entire history of drivers/staging/hv up to 3.4. I had actually thought of this in the past myself as well, but in the end, decided to follow Greg's lead so at least it would be consistent with what is/was done for 2.6.32 P. > > Olaf -- 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