linux-kernel - Re: [PATCH] Removes extra checking kernel/cpuset.c

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] [day] [month] [year] [list]

Message-Id: <20080811224800.ab8e5c79.pj@sgi.com>
Date:	Mon, 11 Aug 2008 22:48:00 -0500
From:	Paul Jackson <pj@....com>
To:	"Rakib Mullick" <rakib.mullick@...il.com>
Cc:	menage@...gle.com, linux-kernel@...r.kernel.org,
	Max Krasnyansky <maxk@...lcomm.com>,
	Li Zefan <lizf@...fujitsu.com>
Subject: Re: [PATCH] Removes extra checking kernel/cpuset.c

This PATCH has the exact same name 'Removes extra checking kernel/cpuset.c'
as another, different PATCH:
  1) sent 7/31: kernel/cpuset.c guarantee_online_mems() and guarantee_online_cpus()
  2) this one, sent 8/2: kernel/cpuset.c update_domain_attr().

Please use different names for different patches.

And this one, for update_domain_attr(), probably conflicts with other
work being done by Max K (I'll add him to the CC list, above) which relies
on this dattr check here, as commented in a recent patch of his:

  cpuset: Rework sched domains and CPU hotplug handling (take 4)

-OR- it conflicts with the code version that Li Zefan was referring
to in his comment:

> The above code no longer exists in latest-git.

I'm not sure which conflict is still relevant here.

How about you wait for the dust to settle on Max K's above patch,
and then consider if this change is still useful?  I suspect it
won't be useful.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.940.382.4214
--
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/