can observe these at
> syscall exit tracing, but they will never be left for the debugged user
> process to see."
Thanks, is that better?
Satoru
---
Add comment for errnos related to restart syscall to avoid the leakage of
them to user programs.
Signed-off-by: Satoru Takeuchi <[E
rqd/2 can't stop becasue that rt process runs everlastingly on CPU0,
and CPU1 waiting the ksoftirqd/2's termination hangs up. To fix this problem,
set
the priority of ksoftirqd/2 to max one before kthread_stop().
Signed-off-by: Satoru Takeuchi <[EMAIL PROTECTED]>
Index: linux-2.
me process which doesn't relinquish CPU time voluntary on
CPU1
... "kstopmachine" can't start to run and the CPU on which stop_machine_run()
is runing
hangs up. To fix this problem, call sched_setscheduler() before waking up
At Fri, 11 May 2007 17:49:20 +0900,
Satoru Takeuchi wrote:
>
> Hi,
>
> I wrote patches which fixes the problem regarding stop_machine_run() and
> cpu hotplug.
Sorry, there were extra tabs. Fixed.
Thanks,
Satoru
---
Fix stop_machine_run() problem with naughty re
Fix Philips UCB1400 driver to use sched_setscheduler() instead of setting
the fields of task_struct directly.
Signed-off-by: Satoru Takeuchi <[EMAIL PROTECTED]>
Index: linux-2.6.21/drivers/input/touchscreen/ucb140
Fix Touchscreen driver for UCB1x00-based touchscreens to use
sched_setscheduler() instead of setting the fields of task_struct directly.
Signed-off-by: Satoru Takeuchi <[EMAIL PROTECTED]>
Index: linux-2.6.21-fix-ucb-drivers/drivers/mfd/ucb1x0
At Sat, 12 May 2007 15:10:27 +0200,
Thomas Gleixner wrote:
>
> On Fri, 2007-05-11 at 19:39 +0900, Satoru Takeuchi wrote:
> > Fix Touchscreen driver for UCB1x00-based touchscreens to use
> > sched_setscheduler() instead of setting the fields of task_struct directly.
> >
&
At Fri, 01 Jun 2007 14:22:03 +0200,
Michal Piotrowski wrote:
> Subject: signal: multithread program returns with wrong errno on
> receiving SIGSTOP
> References : http://lkml.org/lkml/2007/5/27/189
> Submitter : Satoru Takeuchi <[EMAIL PROTECTED]>
> Handled-By :
--
*
* Copyright 2007 Satoru Takeuchi <[EMAIL PROTECTED]>
*
* This software may be used and distributed according to the terms
* of the GNU General Public License, incorporated herein by reference.
*
*/
#include
#include
#include
#include
#include
#include
#include
static int fd[
* strace sleeps on wait4() eternally.
*
* Note
*
*
* This program can't always recreate a problem. However recreate
* possibility is very high.
*
*------
*
* Copyright 2007 Satoru Takeuchi <[EMAIL PROTECTED]>
*
Hi,
At Thu, 7 Jun 2007 02:54:32 -0700 (PDT),
Roland McGrath wrote:
>
> The bug is in strace (and is being fixed). It needs to use tgkill instead
> of kill to send that SIGSTOP to the right thread only.
You mean kill() to specifig thread is fundamentally wrong? If so, current
kill() is wrong
Hi Linus,
At Wed, 6 Jun 2007 08:35:27 -0700 (PDT),
Linus Torvalds wrote:
> On Wed, 6 Jun 2007, Roland McGrath wrote:
> >
> > [PATCH] Restrict clearing TIF_SIGPENDING
> >
> > This patch should get a few birds. It prevents sigaction calls from
> > clearing TIF_SIGPENDING in other threads, which c
Hi Linus,
At Thu, 7 Jun 2007 08:54:33 -0700 (PDT),
Linus Torvalds wrote:
>
>
>
> On Thu, 7 Jun 2007, Satoru Takeuchi wrote:
> >
> > I tested your patch and my problem didn't occur again, so it seems to my
> > this case at least.
>
> Ok. I applied Rola
At Sat, 14 Apr 2007 01:31:12 +1000,
Con Kolivas wrote:
>
> On Monday 09 April 2007 16:09, Andrew Morton wrote:
> > On Sat, 07 Apr 2007 16:31:39 +0900 Satoru Takeuchi
> <[EMAIL PROTECTED]> wrote:
> > > When I was examining the following program ...
> > >
At Mon, 16 Apr 2007 11:16:24 +0900,
Satoru Takeuchi wrote:
>
> At Sat, 14 Apr 2007 01:31:12 +1000,
> Con Kolivas wrote:
> >
> > On Monday 09 April 2007 16:09, Andrew Morton wrote:
> > > On Sat, 07 Apr 2007 16:31:39 +0900 Satoru Takeuchi
> > <[EMAI
At Sat, 14 Apr 2007 14:02:20 +0200,
Ingo Molnar wrote:
>
>
> * [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> > Hi Ingo,
> > Did a test with massive_intr.c on a standard linux desktop.
> > for vanilla, con's Sd-0.40 and cfs.
>
> thanks!
>
> > [EMAIL PROTECTED] tests]$ ./massive_intr 10 10
At Mon, 16 Apr 2007 10:47:25 +0200,
Ingo Molnar wrote:
>
>
> * Satoru Takeuchi <[EMAIL PROTECTED]> wrote:
>
> > > btw., other schedulers might work better with some more test-time:
> > > i'd suggest to use 60 seconds (./massive_intr 10 60) [or maybe mor
At Mon, 16 Apr 2007 14:45:59 +0400,
Oleg Nesterov wrote:
>
> On 04/16, Satoru Takeuchi wrote:
> >
> > --- linux-2.6.21-rc6-mm1.tsfix.orig/kernel/exit.c 2007-04-15
> > 16:56:12.0 +0900
> > +++ linux-2.6.21-rc6-mm1.tsfix/kernel/exit.c2007-04-15
Hi,
I found a bug on 2.6.21 cpu-hotplug code.
When process A on CPU0 try to offline the CPU1 on which the process B,
realtime process (its task->policy == SCHED_FIFO or SCHED_RR) running
without sleep or yield, both CPU0 and CPU1 get hang. It's because of
the following code on __stop_machine_run(
At Mon, 07 May 2007 23:42:53 +1000,
Rusty Russell wrote:
>
> On Mon, 2007-05-07 at 19:10 +0900, Satoru Takeuchi wrote:
> > Hi,
> >
> > I found a bug on 2.6.21 cpu-hotplug code.
> >
> > When process A on CPU0 try to offline the CPU1 on which the process B,
&g
At Tue, 08 May 2007 13:02:25 +1000,
Rusty Russell wrote:
>
> On Tue, 2007-05-08 at 11:41 +0900, Satoru Takeuchi wrote:
> > At Mon, 07 May 2007 23:42:53 +1000,
> > Rusty Russell wrote:
> > > I look forward to your patch!
> > > Rusty.
> >
> > Thanks,
At Tue, 8 May 2007 09:40:33 +0530,
Srivatsa Vaddagiri wrote:
>
> On Tue, May 08, 2007 at 12:29:19PM +0900, Satoru Takeuchi wrote:
> > > We used to be able to create kernel threads higher than any userspace
> > > priority. If this is no longer true, I think that's O
At Tue, 8 May 2007 22:18:50 +0530,
Srivatsa Vaddagiri wrote:
>
> On Tue, May 08, 2007 at 04:16:06PM +0900, Satoru Takeuchi wrote:
> > Sometimes I wonder at prio_array. It has 140 entries(from 0 to 139),
> > and the meaning of each entry is a
At Wed, 09 May 2007 10:47:50 +1000,
Nick Piggin wrote:
>
> Satoru Takeuchi wrote:
> > At Tue, 8 May 2007 22:18:50 +0530,
> > Srivatsa Vaddagiri wrote:
> >
> >>On Tue, May 08, 2007 at 04:16:06PM +0900, Satoru Takeuchi wrote:
> >>
> >>>Sometime
tread creation at best, hmm...
Thanks,
Satoru
/// satprocess.c //
/*
* satprocess - Create child process and wait for it several times. Each child
* process does nothing and exits immediately.
*
* Copyright (C) 2007 Satoru Takeuchi <[EMAIL PROTECTED]>
*
*
At Sat, 07 Apr 2007 16:31:39 +0900,
Satoru Takeuchi wrote:
> Test programs(attached in the mail):
>
> - satprocess.c: Process model. It creates a child process and wait for it
>several times. Each child process exits immediately.
> - satthread.c: T
> > b) Doesn't add extra field and have thread's parent the creater, which is
> > same as process creation. However it has many side effects, for example,
> > we also need to change sys_getppid() implementation.
>
> can't understand this, sorry.
Sorry for my obscure English, perhaps I ne
> > This comes at an awkward time, because we might well merge the
> > staircase/deadline work into 2.6.22, and I think it rewrites the part of
> > the scheduler which is causing the problems you're observing.
> >
> > Has anyone verified that SD fixes this problem and the one at
> > http://lkml.or
Fix wrong comment for syscall stack layout.
`ret_from_sys_call' label no longer exist and `syscall_exit' label was
introduced instead.
Signed-off-by: Satoru Takeuchi <[EMAIL PROTECTED]>
Index: linux-2.6.21/arch/i38
Fix hrtimers documentation.
- The word `patch' is used to indicate hrtimers subsystem implementation.
However this subsystem has already been in ustream kernel, so convert
them into appropriate phrases.
- Some minor cleanups.
Signed-off-by: Satoru Takeuchi <[EMAIL PROTECTED]>
I
ime[sec]
*
* ex) If you want to run 300 processes for 5 mins, issue the
* command as follows:
*
* $ massive_intr 300 300
*
* How to build:
*
* cc -o massive_intr massive_intr.c -lrt
*
*
* Copyright (C) 2007 Sat
Hi Ingo,
At Tue, 27 Mar 2007 21:14:20 +0200,
Ingo Molnar wrote:
>
>
> * Satoru Takeuchi <[EMAIL PROTECTED]> wrote:
>
> > Hi Ingo and all,
> >
> > When I was executing massive interactive processes, I found that some
> > of them occupy CPU time and
Hi Ingo,
> > > Hi Ingo and all,
> > >
> > > When I was executing massive interactive processes, I found that some
> > > of them occupy CPU time and the others hardly run.
> >
> > yeah.
> >
> > > I also attach the test program which easily recreates this problem.
> >
> > thanks, this is really
Hi Mike,
> I puttered around with your testcase a bit, and didn't see interactive
> tasks starving other interactive tasks so much as plain old interactive
> tasks starving expired tasks, which they're supposed to be able to do,
I inserted a trace code observing all context switches into the kern
> next time.
>
> I reproduced ENOMEM case with the following script (need
> CONFIG_FAIL_PAGE_ALLOC, and CONFIG_FAULT_INJECTION_DEBUG_FS).
I confirmed that this problem reproduce with 3.19-rc3 and
not reproduce with 3.19-rc3 with your patch.
Tested-by: Satoru Takeuchi
Thank you for
l:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.tar.xz
- Build Environment:
- OS: Debian Jessy x86_64
- CPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz x 4
- mem
est mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.tar.xz
- Build Environment:
- OS: Debian Jessy x86_64
- CPU: Intel
135 fail: 0
> Qemu tests:
> total: 27 pass: 27 fail: 0
>
> Details are available at http://server.roeck-us.net:8010/builders.
>
> Guenter
Plus, this kernel passed my test.
- Test Cases:
- Build this kernel.
- Boot this kernel.
- Build the latest mainline kernel wit
est mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.xz
- Build Environment:
- OS: Debian Jessy x86_64
- CPU: Intel
From: Satoru Takeuchi
As mentioned at commit 5a5d8e48449, we can't terminate 'virsh console'
with the default signal(INT). So it's better to set CLOSE_CONSOLE_SIGNAL
in the kvm.conf.
Signed-off-by: Satoru Takeuchi
Cc: Steven Rostedt
---
tools/testing/ktest/examples/kvm.c
At Tue, 25 Feb 2014 21:21:18 -0500,
MUNEDA Takahiro wrote:
>
> On Mon, 24 Feb 2014 09:30:39 -0500,
> Steven Rostedt wrote:
>
> > On Sun, 23 Feb 2014 10:19:28 +0900
> > Satoru Takeuchi wrote:
> >
> >> From: Satoru Takeuchi
> >>
> >> As m
At Fri, 1 Nov 2013 14:43:11 -0700,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.4.68 release.
> There are 32 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
Hi,
I wrote a ktest document and published it.
http://www.slideshare.net/satorutakeuchi18/kernel-auto-testbyktest
It's not the ktest reference guild, but the quick learning guild of ktest
especially focuses on some important features.
After reading this document, you'll be able to do the follow
is kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.xz
- Build Environment:
- OS: Debian Jessy x86_64
- CPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10
From: Satoru Takeuchi
If we'd like to set the redirect target file of run_command(),
we should define $redirect before calling this function and should undef it
after calling this function. Since it's user-unfriendly, add 2nd parameter of
run_command() for this purpose.
Signed-off-
From: Satoru Takeuchi
Build failure hapens with the following log if BUILD_DIR is dirty.
===
...
RUNNING TEST 1 of 1 with option build olddefconfig
make O=/home/sat/ktest/output mrproper ... CLEAN arch/x86/tools
At Sun, 2 Mar 2014 08:29:16 -0500,
Steven Rostedt wrote:
>
> On Sun, 02 Mar 2014 21:23:36 +0900
> Satoru Takeuchi wrote:
>
> > From: Satoru Takeuchi
> >
> > Build failure hapens with the following log if BUILD_DIR is dirty.
>
> If you want to do mak
At Thu, 20 Mar 2014 11:55:02 -0400,
Steven Rostedt wrote:
>
> On Sat, 15 Mar 2014 16:22:49 +0900
> Satoru Takeuchi wrote:
>
> > Hi,
> >
> > I wrote a ktest document and published it.
> >
> > http://www.slideshare.net/satorutakeuchi18/kernel-au
uild the latest mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.xz
- Build Environment:
- OS: Debian Jessy x86_64
- CPU: I
kernel.
- Build the latest mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.xz
- Build Environment:
- OS: Debian Je
IRTUAL
...
> Eric W. Biederman
> vfs: In d_path don't call d_dname on a mount point
This kernel also passed my test.
- Test Cases:
- Build this kernel.
- Boot this kernel.
- Build the latest mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.xz
- Build Environment:
- OS: Debian Jessy x86_64
- CPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz x 4
- mem
At Mon, 25 Nov 2013 13:44:29 +,
Ben Hutchings wrote:
>
> This is the start of the stable review cycle for the 3.2.53 release.
> There are 87 patches in this series, which will be posted as responses
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> R
At Wed, 27 Nov 2013 14:45:04 +,
Ben Hutchings wrote:
>
> [1 ]
> [1.1 ]
> This is the combined patch for 3.2.53-rc1 relative to 3.2.52.
This kernel can be built and boot without any problem.
- Build Machine: debian jessy x86_64
CPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz x 4
memory:
At Thu, 28 Nov 2013 08:01:51 +0900,
Satoru Takeuchi wrote:
>
> At Wed, 27 Nov 2013 14:45:04 +,
> Ben Hutchings wrote:
> >
> > [1 ]
> > [1.1 ]
> > This is the combined patch for 3.2.53-rc1 relative to 3.2.52.
>
> This kernel can be built and boot wit
At Tue, 26 Nov 2013 16:56:24 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.4.71 release.
> There are 39 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
At Tue, 26 Nov 2013 16:56:29 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.10.21 release.
> There are 80 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
At Tue, 26 Nov 2013 10:12:10 -0800,
Greg Kroah-Hartman wrote:
>
> -
> NOTE:
> This is the LAST 3.11.x kernel I will be releasing. Everyone should
> be moving to the 3.12.x series at this point in time. After this
> kernel is released, 3.11 will be end-of-lif
At Tue, 26 Nov 2013 16:56:13 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.12.2 release.
> There are 116 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
_CONSOLE_SIGNAL which mean the
signal to terminate the console. Since its default value is "INT",
the original behavior isn't changed.
Signed-off-by: Satoru Takeuchi
Cc: Steven Rostedt
---
tools/testing/ktest/ktest.pl | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
di
kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.xz
- Build Environment:
- OS: Debian Jessy x86_64
- CPU: Intel(R) Core(TM) i
At Fri, 8 Nov 2013 22:51:29 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.4.69 release.
> There are 26 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
At Fri, 8 Nov 2013 22:51:05 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.10.19 release.
> There are 74 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
At Fri, 8 Nov 2013 22:51:06 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.11.8 release.
> There are 94 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
T
At Mon, 18 Nov 2013 10:41:33 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.4.70 release.
> There are 12 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
At Mon, 18 Nov 2013 10:42:10 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.10.20 release.
> There are 24 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
At Mon, 18 Nov 2013 10:40:29 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.11.9 release.
> There are 25 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
At Mon, 18 Nov 2013 10:37:13 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.12.1 release.
> There are 19 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
Hi Greg, stable guys and all,
I released the stable kernel auto testing tool based on ktest.
https://github.com/satoru-takeuchi/test-linux-stable
After several configration, you can test any stable-rc kernels
by the following command. Just one command
At Mon, 2 Dec 2013 11:05:41 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.4.72 release.
> There are 60 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
At Mon, 2 Dec 2013 11:09:43 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.10.22 release.
> There are 173 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
At Mon, 2 Dec 2013 11:13:11 -0800,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.12.3 release.
> There are 212 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
his kernel.
- Boot this kernel.
- Build the latest mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.tar.xz
- Build Environ
est mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.tar.xz
- Build Environment:
- OS: Debian Jessy x86_64
- CPU: Intel
ss: 139 fail: 0
>
> Qemu tests all passed.
>
> Details are available at http://server.roeck-us.net:8010/builders.
>
> Guenter
This kernel passed my test.
- Test Cases:
- Build this kernel.
- Boot this kernel.
- Build the latest mainline kernel with this kernel.
- Test
ith this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.tar.xz
- Build Environment:
- OS: Debian Jessy x86_64
- CPU: Intel(R) Core(TM) i5-2400
- Test Cases:
- Build this kernel.
- Boot this kernel.
- Build the latest mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/r
- Build this kernel.
- Boot this kernel.
- Build the latest mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.tar.xz
- Bu
Hi,
I revised ktest documentation.
v1.1.2->v1.1.3: Support not only debian/jessy, but also CentOS7 as target system
http://www.slideshare.net/satorutakeuchi18/kernel-auto-testbyktest
It's not the ktest reference guild, but the quick learning guild of ktest
especially focuses on some important f
he diffstat can be found below.
All 3.10.55-rc1, 3.14.19-rc1, and 3.6.3-rc1 passed my test.
- Test Cases:
- Build this kernel.
- Boot this kernel.
- Build the latest mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kerne
Hi Steven,
At Sun, 02 Mar 2014 21:20:31 +0900,
Satoru Takeuchi wrote:
>
> From: Satoru Takeuchi
>
> If we'd like to set the redirect target file of run_command(),
> we should define $redirect before calling this function and should undef it
> after calling this fu
At Fri, 7 Mar 2014 19:43:28 -0500,
Steven Rostedt wrote:
>
> On Sat, 08 Mar 2014 09:12:31 +0900
> Satoru Takeuchi wrote:
>
> > Hi Steven,
> >
> > At Sun, 02 Mar 2014 21:20:31 +0900,
> > Satoru Takeuchi wrote:
> > >
> > > From: Satoru T
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.xz
- Build Environment:
- OS: Debian Jessy x86_64
- CPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz x 4
- mem
At Sat, 08 Mar 2014 09:10:00 -0800,
Guenter Roeck wrote:
>
> On 03/08/2014 08:18 AM, Greg Kroah-Hartman wrote:
> > On Sat, Mar 08, 2014 at 06:35:52AM -0800, Guenter Roeck wrote:
> >> On 03/08/2014 01:47 AM, Satoru Takeuchi wrote:
> >>> At Fri, 7 Mar 2014 17:06:5
From: Satoru Takeuchi
If we'd like to set the redirect target file of run_command(),
we should define $redirect before this function and should undef it after
this function. Since it's user-unfriendly, add 2nd parameter of
run_command() for this purpose.
Signed-off-by: Satoru Ta
From: Satoru Takeuchi
Some cleanup for improving readability as follows.
- Initialize $ktest_config at its definition.
- Put parentheses around the `config-file' argument in the usage message
because it's a optional one.
- Rename get_ktest_config{,s} to more d
From: Satoru Takeuchi
Each test of ktest consists of the following steps.
build -> install -> boot -> run user defined tests.
$buildonly means not whether the test is build onlyor not. Actually
this variable mean the last step of the test as follows.
0: boot or more
1: build
2
At Mon, 10 Mar 2014 12:13:00 -0400,
Steven Rostedt wrote:
>
> On Sun, 09 Mar 2014 23:36:49 +0900
> Satoru Takeuchi wrote:
>
> > From: Satoru Takeuchi
> >
> > Each test of ktest consists of the following steps.
> >
> > build -> install -> boo
At Tue, 11 Mar 2014 20:43:40 +0900,
Satoru Takeuchi wrote:
>
> At Mon, 10 Mar 2014 12:13:00 -0400,
> Steven Rostedt wrote:
> >
> > On Sun, 09 Mar 2014 23:36:49 +0900
> > Satoru Takeuchi wrote:
> >
> > > From: Satoru Takeuchi
> > >
>
tecture.
>
> Guenter
>
This kernel passed my test.
- Test Cases:
- Build this kernel.
- Boot this kernel.
- Build the latest mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config
nel.
- Build the latest mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.tar.xz
- Build Environment:
- OS: Debian Jessy x8
and 3.14.1-rc1 passed my test.
- Test Cases:
- Build this kernel.
- Boot this kernel.
- Build the latest mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuch
ainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.tar.xz
- Build Environment:
- OS: Debian Jessy x86_64
- CPU: Intel
At Sun, 23 Mar 2014 15:54:04 +0800,
Liu Hua wrote:
>
> As sysctl_hung_task_timeout_sec is unsigned long, when this value is
> larger then LONG_MAX/HZ, the function schedule_timeout_interruptible in
> watchdog will return immediately without sleep and with print :
>
> [ 205.452934] schedule_timeo
At Tue, 25 Mar 2014 16:58:58 +0800,
Liu hua wrote:
>
> δΊ 2014/3/24 4:50, Satoru Takeuchi ει:
> > At Sun, 23 Mar 2014 15:54:04 +0800,
> > Liu Hua wrote:
> >>
> >> As sysctl_hung_task_timeout_sec is unsigned long, when this value is
> &
est mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/-.tar.xz
- Build Environment:
- OS: Debian Jessy x86_64
- CPU: Intel
gt; let me know.
>
> Responses should be made by Wed Jul 2 11:49:58 2014
> Anything received after that time might be too late.
This kernel passed my test.
- Test Cases:
- Build this kernel.
- Boot this kernel.
- Build the latest mainline kernel with this kernel.
- Test Tool:
h
(2014/07/02 9:01), David Sterba wrote:
On Wed, Jun 25, 2014 at 08:35:43PM +0200, Fabian Frederick wrote:
kcalloc manages count*sizeof overflow.
Cc: Chris Mason
Cc: Josef Bacik
Cc: linux-bt...@vger.kernel.org
Signed-off-by: Fabian Frederick
Reviewed-by: David Sterba
Reviewed-by: Satoru
3.15.3-rc1, 3.14.10-rc1, 3.10.46-r1, and 3.4.96-rc1 passed my test.
- Test Cases:
- Build this kernel.
- Boot this kernel.
- Build the latest mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, kte
sappeared.
- Test Cases:
- Build this kernel.
- Boot this kernel.
- Build the latest mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-st
101 - 200 of 252 matches
Mail list logo
