linux-kernel - Re: [PATCH] Code clean up for percpu

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:	Tue, 18 Oct 2011 09:33:21 -0500 (CDT)
From:	Christoph Lameter <cl@...two.org>
To:	"Alex,Shi" <alex.shi@...el.com>
cc:	"tj@...nel.org" <tj@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"eric.dumazet@...il.com" <eric.dumazet@...il.com>,
	"Huang, Ying" <ying.huang@...el.com>
Subject: Re: [PATCH] Code clean up for percpu_xxx() functions

On Tue, 18 Oct 2011, Alex,Shi wrote:

> > I think its good to have it all in a single patch.
> >
>
> I thought over your requirements, but it is difficult for me to know
> lots of fields in kernel, like for xen/kvm/network etc. So, to avoid
> introduce bugs here, could we do this blind changes, and then change
> each of fields and get owner's ack separately.

Well do the obvious (where you can see that interrupts or preemption are
disabled in the function or in a calling function). Leave the rest as is
and provide separate patches for them?
--
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/