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]
Date:	Mon, 23 Nov 2015 22:14:08 +0800
From:	Fengguang Wu <lkp@...el.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-rt-users@...r.kernel.org, bigeasy@...utronix.de,
	linux-kernel@...r.kernel.org, kbuild-all@...org,
	jianchuan.wang@...driver.com, tglx@...utronix.de,
	yang.shi@...driver.com
Subject: Re: [kbuild-all] [PATCH] locking_selftest: Save/restore
 migrate_disable_atomic in locking selftest

On Mon, Nov 23, 2015 at 08:43:25AM -0500, Steven Rostedt wrote:
> On Mon, 23 Nov 2015 15:30:30 +0800
> kbuild test robot <lkp@...el.com> wrote:
> 
> > Hi Jianchuan,
> > 
> > [auto build test ERROR on: v4.4-rc2]
> > [also build test ERROR on: next-20151120]
> > 
> > url:    https://github.com/0day-ci/linux/commits/jianchuan-wang-windriver-com/locking_selftest-Save-restore-migrate_disable_atomic-in-locking-selftest/20151123-152217
> > config: x86_64-randconfig-x013-11230343 (attached as .config)
> > reproduce:
> >         # save the attached .config to linux build tree
> >         make ARCH=x86_64 
> > 
> > All errors (new ones prefixed by >>):
> > 
> >    lib/locking-selftest.c: In function 'dotest':
> > >> lib/locking-selftest.c:981:25: error: 'struct task_struct' has no member named 'migrate_disable_atomic'  
> >      save_migrate_atomic = p->migrate_disable_atomic;
> >                             ^
> >    lib/locking-selftest.c:987:3: error: 'struct task_struct' has no member named 'migrate_disable_atomic'
> >      p->migrate_disable_atomic = save_migrate_atomic;
> >       ^
> 
> 
> Need to add RT in the subject like "[PATCH RT]". Then perhaps Fengguang
> can have his tests either ignore these or test against the -rt trees.

Yes sure. Shall I apply RT patches to this tree/branch?

https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git linux-4.1.y-rt

Thanks,
Fengguang
--
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