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] [day] [month] [year] [list]
Message-ID: <20160125060511.GE4503@linux.vnet.ibm.com>
Date:	Sun, 24 Jan 2016 22:05:11 -0800
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	"Huang, Ying" <ying.huang@...el.com>
Cc:	Davidlohr Bueso <dave@...olabs.net>,
	Waiman Long <Waiman.Long@...com>,
	Peter Zijlstra <peterz@...radead.org>, lkp@...org,
	Will Deacon <will.deacon@....com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...hat.com>,
	Ding Tianhong <dingtianhong@...wei.com>,
	Thomas Gleixner <tglx@...utronix.de>, fengguang.wu@...el.com,
	Tim Chen <tim.c.chen@...ux.intel.com>,
	Jason Low <jason.low2@...com>
Subject: Re: [LKP] [lkp] [locking/mutexes] cb4bbc457b: -40.0% unixbench.score

On Mon, Jan 25, 2016 at 09:23:59AM +0800, Huang, Ying wrote:
> Davidlohr Bueso <dave@...olabs.net> writes:
> 
> > On Fri, 22 Jan 2016, kernel test robot wrote:
> >
> >>FYI, we noticed the below changes on
> >>
> >>https://github.com/0day-ci/linux
> >> Ding-Tianhong/locking-mutexes-don-t-spin-on-owner-when-wait-list-is-not-NULL/20160121-173317
> >>commit cb4bbc457bfed6194ffab1b10c7be73b3f16ca2d ("locking/mutexes: don't spin on owner when wait list is not NULL.")
> >
> > I'm not sure why this would even be reported, as this patch has not been accepted
> > or acked or nothin', by anyone.
> 
> Sorry for bothering.  The purpose is FYI as in the original report
> email.  We test patches posted to LKML, if we found some changes related
> to the patch, we will send out a report.  Hope the reviewer could
> take that as information for his/her review if the report isn't totally
> nonsense.

For me, the 0day reports on LKML postings have been quite helpful.  They
give the submitter immediate feedback on a number of issues, thus reducing
the number of rounds of review.

								Thanx, Paul

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ