This patch just trivial converts from calling kernel_thread and daemonize
to just calling kthread_run.
Cc: Andi Kleen <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
arch/i386/kernel/io_apic.c |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
thread_run is used intead of kernel_thread, daemonize, and mucking
around blocking signals directly.
CC: David Woodhouse <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
drivers/mtd/mtd_blkdevs.c | 19 +-
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
kthread_run replaces the kernel_thread and daemonize calls
during thread startup.
Calls to signal_pending were also removed as it is currently
impossible for the cpci_hotplug thread to receive signals.
CC: Scott Murray <[EMAIL PROTECTED]>
S
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
kthread_run replaces kernel_thread and dameonize.
allow_signal is unnecessary and has been removed.
tid_poll was unused and has been removed.
Cc: Jyoti Shah <[EMAIL PROTECTED]>
Cc: Greg Kroah-Hartman <[EMAIL PROTECTED]>
Signed-off-by: Eric W
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch just trivially replaces kernel_thread and daemonize
with a single call to kthread_run.
CC: James Bottomley <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
arch/i386/mach-voyager/voyager_thread.c |5
On Thu, 2007-04-19 at 10:41 +1000, Con Kolivas wrote:
> Mike you were the stick.
(dirty job, somebody has to do it)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-inf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch starts up khidp using kthread_run instead
of kernel_thread and daemonize, resulting is slightly
simpler and more maintainable code.
Cc: Marcel Holtmann <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
n
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
It is my goal to replace all kernel code that handles signals
from user space, calls kernel_thread or calls daemonize. All
of which the kthread_api makes unncessary. Handling signals
from user space is a maintenance problem becuase using a
k
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
Modify startup of ipvs sync threads to use kthread_run
instead of a weird combination of calling kernel_thread
to start a fork_sync_thread whose hole purpose in life was
to call kernel_thread again starting the actually sync thread
which calle
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
To start the nfsv4-delegreturn thread this patch uses
kthread_run instead of a combination of kernel_thread
and daemonize.
In addition allow_signal(SIGKILL) is removed from
the expire delegations thread.
Cc: Neil Brown <[EMAIL PROTECTED]>
Cc
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
Cc: Neil Brown <[EMAIL PROTECTED]>
Cc: Trond Myklebust <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
fs/nfsd/nfs4state.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/fs/nfsd/nfs4stat
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
Start the reclaimer thread using kthread_run instead
of a combination of kernel_thread and daemonize.
The small amount of signal handling code is also removed
as it makes no sense and is a maintenance problem to handle
signals in kernel thread
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch starts krfcommd using kthread_run instead of a combination
of kernel_thread and daemonize making the code slightly simpler
and more maintainable.
Cc: Marcel Holtmann <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROT
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
Use kthread_run to start the lcs kernel threads not a
combination of kernel_thread and daemonize. This makes
the code slightly simpler and more maintainable.
Cc: Frank Pavlic <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTE
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patches modifies the pnpbios kernel thread to start
with ktrhead_run not kernel_thread and deamonize. Doing
this makes the code a little simpler and easier to maintain.
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
drivers/p
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This starts the sparc64 powerd using kthread_run
instead of kernel_thread and daemonize. Making the
code slightly simpler and more maintainable.
In addition the unnecessary flush_signals is removed.
Cc: David S. Miller <[EMAIL PROTECTED]>
S
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch modifies the sas scsi host thread startup
to use kthread_run not kernel_thread and deamonize.
kthread_run is slightly simpler and more maintainable.
Cc: Darrick J. Wong <[EMAIL PROTECTED]>
Cc: James Bottomley <[EMAIL PROTECTED]>
Si
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch changes cpqphp to use kthread_run and not
kernel_thread and daemonize to startup and setup
the cpqphp thread.
Cc: Greg Kroah-Hartman <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
drivers/pci/hotplug/
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch modifies the startup of kafscmd, kafsasyncd, and kafstimod
to use kthread_run instead of a combination of kernel_thread and
daemonize making the code slightly simpler and more maintainable.
In addition since by default all signals
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch starts the xpc kernel threads using kthread_run
not a combination of kernel_thread and daemonize. Resuling
in slightly simpler and more maintainable code.
Cc: Jes Sorensen <[EMAIL PROTECTED]>
Cc: Tony Luck <[EMAIL PROTECTED]>
Sign
* Nigel Cunningham <[EMAIL PROTECTED]> wrote:
> From subsequent emails, I think you already got your answer, but just
> in case...
>
> Yes, if you enabled "Replace swsusp by default" and you already had it
> set up for getting swsusp to resume. If not, and you're using an
> initrd/ramfs, you'
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch modifies the startup of kecardd to use
kthread_run not a kernel_thread combination of kernel_thread
and daemonize. Making the code slightly simpler and more
maintainable.
Cc: Russell King <[EMAIL PROTECTED]>
Signed-off-by: Eric W.
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch modifies the startup of eehd to use kthread_run
not a combination of kernel_thread and daemonize. Making
the code slightly simpler and more maintainable.
Cc: Paul Mackerras <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EM
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch modifies the qeth_recover thread to be started
with kthread_run not a combination of kernel_thread and
daemonize. Resulting in slightly simpler and more maintainable
code.
Cc: Frank Pavlic <[EMAIL PROTECTED]>
Signed-off-by: Eric W
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
Modify zfcperp%s to be started with kthread_run not
a combination of kernel_thread, daemonize and siginitsetinv
making the code slightly simpler and more maintainable.
Cc: Swen Schillig <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[E
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch modifies the startup of krxtimod, krxiod, and krxsecd
to use kthread_run instead of a combination of kernel_thread
and daemonize making the code slightly simpler and more maintainable.
In addition since by default all signals are i
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch starts kbenpd using kthread_run replacing
a combination of kernel_thread and daemonize. Making
the code a little simpler and more maintainable.
Cc: Marcel Holtmann <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTE
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch modifies the kcmptd_ctr_%d daemon using kthread_run
instead of a combination of kernel_thread and daemonize making
the code a little simpler and more maintainable.
Cc: Marcel Holtmann <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Bied
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch modifies the startup of the media_bay_task
to use kthread_run and not a combination of kernel_thread,
deamonize and sigfillset.
In addition since we now always want to ignore signals
the MB_IGNORE_SIGNALS define is removed along wi
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
Currently md_thread calls allow_signal so it can receive a
SIGKILL but then does nothing with it except flush the
sigkill so that it not can use an interruptible sleep.
This whole dance is silly so remove the unnecessary
and broken signal han
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch modifies startup of the kfand to use kthread_run
not a combination of kernel_thread and daemonize, making
the code a little simpler and more maintaintable.
Cc: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biede
* Mike Galbraith <[EMAIL PROTECTED]> wrote:
> With a heavily reniced X (perfectly fine), that should indeed solve my
> daily usage pattern nicely (always need godmode for shells, but not
> for mozilla and ilk. 50/50 split automatic without renice of entire
> gui)
how about the first-approxima
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch is a minimal transformation to use the kthread API
doing it's best to preserve the existing logic.
Instead of starting kdvb-ca by calling kernel_thread,
daemonize and sigfillset we kthread_run is used.
Instead of tracking the pid
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch modifies the startup of kadbprobe to use
kthread_run instead of scheduling a work event which
later calls kernel_thread and in the thread calls
daemonize and blocks signals. kthread_run is simpler
and more maintainable.
The variab
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
This patch modifies the startup of rtasd to use kthread_run instaed of
a combination of kernel_thread and daemonize. Making the code a little
simpler and more maintainble.
Cc: Paul Mackerras <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederm
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
Start the g4fand using kthread_run not a combination
of kernel_thread and deamonize. This makes the code
a little simpler and more maintainable.
Cc: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTE
Abhijit Bhopatkar wrote:
In my mind i find it fundamentally wrong to separate anon pages from
page cache. It should rather be lot more dependent on which task
accessed them last. Although it seems due to some twisted relationships
bet anon pages and interactive tasks separating them improves it.
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
Cc: Neil Brown <[EMAIL PROTECTED]>
Cc: Trond Myklebust <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
fs/nfs/nfs4state.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/fs/nfs/nfs4state.
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
Cc: David Howells <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
kernel/synchro-test.c | 16 ++--
1 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/kernel/synchro-test.c b/kernel/synch
From: Eric W. Biederman <[EMAIL PROTECTED]> - unquoted
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
fs/smbfs/smbiod.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/fs/smbfs/smbiod.c b/fs/smbfs/smbiod.c
index 3e61b44..67176af 100644
--- a/fs/smbfs/smbiod.c
+
On Thu, 2007-04-19 at 08:52 +0200, Mike Galbraith wrote:
> On Wed, 2007-04-18 at 23:48 +0200, Ingo Molnar wrote:
>
> > so my current impression is that we want per UID accounting to solve the
> > X problem, the kernel threads problem and the many-users problem, but
> > i'd not want to do it for
A fixed version of the patch shutting up missing version warnings when building
mandocs.
Signed-off-by: Borislav Petkov <[EMAIL PROTECTED]>
Index: 21-rc7/scripts/kernel-doc
===
--- 21-rc7.orig/scripts/kernel-doc
+++ 21-rc7/scripts/k
On Apr 18 2007 09:39, Stephen Clark wrote:
>>
> So this is the pop I hear on my new laptop that is using
> libata=combined_mode when I shut my system down. I didn't get the
> pop with the same disk drive in an older laptop that was only ide.
> It sounds like a relay closing or opening, but is real
On Thu, 2007-04-19 at 09:09 +0200, Ingo Molnar wrote:
> * Mike Galbraith <[EMAIL PROTECTED]> wrote:
>
> > With a heavily reniced X (perfectly fine), that should indeed solve my
> > daily usage pattern nicely (always need godmode for shells, but not
> > for mozilla and ilk. 50/50 split automatic
* Jarek Poplawski <[EMAIL PROTECTED]> wrote:
> + int i = 1000;
>
> - while (!cancel_delayed_work(dwork))
> + while (!cancel_delayed_work(dwork)) {
> flush_workqueue(wq);
> + BUG_ON(!i--);
> + }
if then ma
On Apr 18 2007 10:45, david rankin wrote:
>
> Mates,
>
> First post and I am having heck building the vanilla 2.6.20.7 kernel on
> Suse 10.0. Basically I put 2.6.20.7 in /usr/src, then I did
>[...]
> All current minimal requierments are met *except* udev which is version
> 068. Everything comp
On Thu, 19 Apr 2007 09:35:58 +0530, Milind Arun Choudhary wrote:
> SPIN_LOCK_UNLOCKED cleanup,use __SPIN_LOCK_UNLOCKED instead
>
> Signed-off-by: Milind Arun Choudhary <[EMAIL PROTECTED]>
>
> ---
> i2c-pxa.c |2 +-
> i2c-s3c2410.c |2 +-
> 2 files changed, 2 insertions(+), 2 deletio
Hi,
Doing some testing on CFQ, I ran into this 100% reproducible report:
===
[ INFO: possible circular locking dependency detected ]
2.6.21-rc7 #5
---
fio/9741 is trying to acquire lock:
(&mm-
I'm looking for a little advice on writing a driver for the Phillips
sc16is752 SPI UART chip. I've written drivers before but I'm having a
problem with this one. Since this driver is both an SPI driver and a
UART driver I'm unclear on whether it should register with
spi_register_driver() or uart_r
Christoph Lameter wrote:
On Wed, 18 Apr 2007, Ethan Solomita wrote:
Any new ETA? I'm trying to decide whether to go back to your original
patches or wait for the new set. Adding new knobs isn't as important to me as
having something that fixes the core problem, so hopefully this isn't wai
* Andrew Morton <[EMAIL PROTECTED]> wrote:
>> Yes, there are potential compatibility problems. Example: a machine
>> with 100 busy httpd processes and suddenly a big gzip starts up from
>> console or cron.
[...]
On Thu, Apr 19, 2007 at 08:38:10AM +0200, Ingo Molnar wrote:
> h. How about the
* Davide Libenzi <[EMAIL PROTECTED]> wrote:
> > That's one reason why i dont think it's necessarily a good idea to
> > group-schedule threads, we dont really want to do a per thread group
> > percpu_alloc().
>
> I still do not have clear how much overhead this will bring into the
> table, but
On Thu, 19 Apr 2007 09:38:30 +0200 Jens Axboe <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Doing some testing on CFQ, I ran into this 100% reproducible report:
>
> ===
> [ INFO: possible circular locking dependency detected ]
> 2.6.21-rc7 #5
>
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch just trivially replaces kernel_thread and daemonize
with a single call to kthread_run.
CC: James Bottomley <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
arch/i386/mach-voyager/voyager_thread.c |5 ++---
1 f
From: Eric W. Biederman <[EMAIL PROTECTED]>
kthread_run replaces kernel_thread and dameonize.
allow_signal is unnecessary and has been removed.
tid_poll was unused and has been removed.
Cc: Jyoti Shah <[EMAIL PROTECTED]>
Cc: Greg Kroah-Hartman <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patches modifies the pnpbios kernel thread to start
with ktrhead_run not kernel_thread and deamonize. Doing
this makes the code a little simpler and easier to maintain.
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
drivers/pnp/pnpbios/
This patch just trivial converts from calling kernel_thread and daemonize
to just calling kthread_run.
Cc: Andi Kleen <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
arch/i386/kernel/io_apic.c |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git
From: Eric W. Biederman <[EMAIL PROTECTED]>
Cc: Neil Brown <[EMAIL PROTECTED]>
Cc: Trond Myklebust <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
fs/nfsd/nfs4state.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/fs/nfsd/nfs4state.c b/fs/nf
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch starts up khidp using kthread_run instead
of kernel_thread and daemonize, resulting is slightly
simpler and more maintainable code.
Cc: Marcel Holtmann <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
net/bluetoot
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch starts krfcommd using kthread_run instead of a combination
of kernel_thread and daemonize making the code slightly simpler
and more maintainable.
Cc: Marcel Holtmann <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch modifies the qeth_recover thread to be started
with kthread_run not a combination of kernel_thread and
daemonize. Resulting in slightly simpler and more maintainable
code.
Cc: Frank Pavlic <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman
From: Eric W. Biederman <[EMAIL PROTECTED]>
Cc: David Howells <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
kernel/synchro-test.c | 16 ++--
1 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/kernel/synchro-test.c b/kernel/synchro-test.c
i
On 4/17/07, David Brownell <[EMAIL PROTECTED]> wrote:
In this case I'm not entirely sure how it'd work. I've seen a few
drivers which let userspace peek and poke at GPIO signals -- like
one for Gumstix boards -- but generalizing the model isn't simple.
Sub-problems include:
- Configuring the r
From: Eric W. Biederman <[EMAIL PROTECTED]>
This starts the sparc64 powerd using kthread_run
instead of kernel_thread and daemonize. Making the
code slightly simpler and more maintainable.
In addition the unnecessary flush_signals is removed.
Cc: David S. Miller <[EMAIL PROTECTED]>
Signed-off-b
From: Eric W. Biederman <[EMAIL PROTECTED]>
Modify zfcperp%s to be started with kthread_run not
a combination of kernel_thread, daemonize and siginitsetinv
making the code slightly simpler and more maintainable.
Cc: Swen Schillig <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTEC
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch changes cpqphp to use kthread_run and not
kernel_thread and daemonize to startup and setup
the cpqphp thread.
Cc: Greg Kroah-Hartman <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
drivers/pci/hotplug/cpqphp_ctrl
From: Eric W. Biederman <[EMAIL PROTECTED]>
thread_run is used intead of kernel_thread, daemonize, and mucking
around blocking signals directly.
CC: David Woodhouse <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
drivers/mtd/mtd_blkdevs.c | 19 +--
On 4/17/07, Roland Dreier <[EMAIL PROTECTED]> wrote:
> > It seems trivial to keep the last key you were given and do a quick
> > memcmp in your setkey method to see if it's different from the last
> > key you pushed to hardware, and set a flag if it is. Then only do
> > your set_key() if you
From: Eric W. Biederman <[EMAIL PROTECTED]>
It is my goal to replace all kernel code that handles signals
from user space, calls kernel_thread or calls daemonize. All
of which the kthread_api makes unncessary. Handling signals
from user space is a maintenance problem becuase using a
kernel threa
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch is a minimal transformation to use the kthread API
doing it's best to preserve the existing logic.
Instead of starting kdvb-ca by calling kernel_thread,
daemonize and sigfillset we kthread_run is used.
Instead of tracking the pid of the runn
From: Eric W. Biederman <[EMAIL PROTECTED]>
Use kthread_run to start the lcs kernel threads not a
combination of kernel_thread and daemonize. This makes
the code slightly simpler and more maintainable.
Cc: Frank Pavlic <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch modifies the startup of eehd to use kthread_run
not a combination of kernel_thread and daemonize. Making
the code slightly simpler and more maintainable.
Cc: Paul Mackerras <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECT
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch modifies the startup of kadbprobe to use
kthread_run instead of scheduling a work event which
later calls kernel_thread and in the thread calls
daemonize and blocks signals. kthread_run is simpler
and more maintainable.
The variable pid_t ad
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch modifies the sas scsi host thread startup
to use kthread_run not kernel_thread and deamonize.
kthread_run is slightly simpler and more maintainable.
Cc: Darrick J. Wong <[EMAIL PROTECTED]>
Cc: James Bottomley <[EMAIL PROTECTED]>
Signed-off-by
From: Eric W. Biederman <[EMAIL PROTECTED]>
kthread_run replaces the kernel_thread and daemonize calls
during thread startup.
Calls to signal_pending were also removed as it is currently
impossible for the cpci_hotplug thread to receive signals.
CC: Scott Murray <[EMAIL PROTECTED]>
Signed-off-b
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch modifies startup of the kfand to use kthread_run
not a combination of kernel_thread and daemonize, making
the code a little simpler and more maintaintable.
Cc: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAI
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch starts the xpc kernel threads using kthread_run
not a combination of kernel_thread and daemonize. Resuling
in slightly simpler and more maintainable code.
Cc: Jes Sorensen <[EMAIL PROTECTED]>
Cc: Tony Luck <[EMAIL PROTECTED]>
Signed-off-by:
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch modifies the startup of krxtimod, krxiod, and krxsecd
to use kthread_run instead of a combination of kernel_thread
and daemonize making the code slightly simpler and more maintainable.
In addition since by default all signals are ignored when
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch modifies the startup of kafscmd, kafsasyncd, and kafstimod
to use kthread_run instead of a combination of kernel_thread and
daemonize making the code slightly simpler and more maintainable.
In addition since by default all signals are ignored
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch modifies the kcmptd_ctr_%d daemon using kthread_run
instead of a combination of kernel_thread and daemonize making
the code a little simpler and more maintainable.
Cc: Marcel Holtmann <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMA
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch modifies the startup of the media_bay_task
to use kthread_run and not a combination of kernel_thread,
deamonize and sigfillset.
In addition since we now always want to ignore signals
the MB_IGNORE_SIGNALS define is removed along with the
test
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch modifies the startup of rtasd to use kthread_run instaed of
a combination of kernel_thread and daemonize. Making the code a little
simpler and more maintainble.
Cc: Paul Mackerras <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch starts kbenpd using kthread_run replacing
a combination of kernel_thread and daemonize. Making
the code a little simpler and more maintainable.
Cc: Marcel Holtmann <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
From: Eric W. Biederman <[EMAIL PROTECTED]>
This patch modifies the startup of kecardd to use
kthread_run not a kernel_thread combination of kernel_thread
and daemonize. Making the code slightly simpler and more
maintainable.
Cc: Russell King <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman
From: Eric W. Biederman <[EMAIL PROTECTED]>
Start the g4fand using kthread_run not a combination
of kernel_thread and deamonize. This makes the code
a little simpler and more maintainable.
Cc: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
dr
From: Eric W. Biederman <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
fs/smbfs/smbiod.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/fs/smbfs/smbiod.c b/fs/smbfs/smbiod.c
index 3e61b44..67176af 100644
--- a/fs/smbfs/smbiod.c
+++ b/fs/smb
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Eric W. Biederman <[EMAIL PROTECTED]>
To start the nfsv4-delegreturn thread this patch uses
kthread_run instead of a combination of kernel_thread
and daemonize.
In addition allow_signal(SIGKILL) is removed from
the expire delegations thread.
Cc: Neil Brown <[EMAIL PROTECTED]>
Cc: Trond Myk
From: Eric W. Biederman <[EMAIL PROTECTED]>
Start the reclaimer thread using kthread_run instead
of a combination of kernel_thread and daemonize.
The small amount of signal handling code is also removed
as it makes no sense and is a maintenance problem to handle
signals in kernel threads.
Cc: Nei
On Thu, Apr 19 2007, Andrew Morton wrote:
> On Thu, 19 Apr 2007 09:38:30 +0200 Jens Axboe <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > Doing some testing on CFQ, I ran into this 100% reproducible report:
> >
> > ===
> > [ INFO: possible circula
From: Eric W. Biederman <[EMAIL PROTECTED]>
Currently md_thread calls allow_signal so it can receive a
SIGKILL but then does nothing with it except flush the
sigkill so that it not can use an interruptible sleep.
This whole dance is silly so remove the unnecessary
and broken signal handling logic
From: Eric W. Biederman <[EMAIL PROTECTED]>
Modify startup of ipvs sync threads to use kthread_run
instead of a weird combination of calling kernel_thread
to start a fork_sync_thread whose hole purpose in life was
to call kernel_thread again starting the actually sync thread
which called daemonize
From: Eric W. Biederman <[EMAIL PROTECTED]>
Cc: Neil Brown <[EMAIL PROTECTED]>
Cc: Trond Myklebust <[EMAIL PROTECTED]>
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
fs/nfs/nfs4state.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/fs/nfs/nfs4state.c b/fs/nfs/
ACK for both patches,
thank you Eric for the patches, will add them to my patchset
for Jeff.
Frank
On Thu, Apr 19, 2007 at 01:58:40AM -0600, Eric W. Biederman wrote:
> From: Eric W. Biederman <[EMAIL PROTECTED]>
>
> Use kthread_run to start the lcs kernel threads not a
> combination of kernel
On Thu, Apr 19, 2007 at 09:32:22AM +0200, Ingo Molnar wrote:
>
> * Jarek Poplawski <[EMAIL PROTECTED]> wrote:
>
> > + int i = 1000;
> >
> > - while (!cancel_delayed_work(dwork))
> > + while (!cancel_delayed_work(dwork)) {
> > flush_workqueue(wq)
On Thu, 19 Apr 2007 10:01:57 +0200 Jens Axboe <[EMAIL PROTECTED]> wrote:
> On Thu, Apr 19 2007, Andrew Morton wrote:
> > On Thu, 19 Apr 2007 09:38:30 +0200 Jens Axboe <[EMAIL PROTECTED]> wrote:
> >
> > > Hi,
> > >
> > > Doing some testing on CFQ, I ran into this 100% reproducible report:
> > >
On Thu, Apr 19, 2007 at 08:38:10AM +0200, Ingo Molnar wrote:
>
> * Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > > And yes, by fairly, I mean fairly among all threads as a base
> > > resource class, because that's what Linux has always done
> >
> > Yes, there are potential compatibility proble
On Thu, Apr 19 2007, Andrew Morton wrote:
> On Thu, 19 Apr 2007 10:01:57 +0200 Jens Axboe <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Apr 19 2007, Andrew Morton wrote:
> > > On Thu, 19 Apr 2007 09:38:30 +0200 Jens Axboe <[EMAIL PROTECTED]> wrote:
> > >
> > > > Hi,
> > > >
> > > > Doing some testing
> > > As I said earlier, I see a case where two mounts that are peers of each
> > > other can become un-identical if we dont propagate the "allowusermnt".
> > >
> > > As a practical example.
> > >
> > > /tmp and /mnt are peers of each other.
> > > /tmp has its "allowusermnt" flag set, which has n
1 - 100 of 484 matches
Mail list logo
