Make getcwd() fail with -ENOENT if the current working directory is
disconnected: the process is not asking for some previous name of that
directory but for the current name; returning a path meaningless in the
context of that process makes no sense.
Signed-off-by: Andreas Gruenbacher <[EMAIL
On Tuesday 17 April 2007 19:21, Alan Cox wrote:
> Can you prove no existing application on the planet relies on the
> existing behaviour ? Actually more limited but sane as a test would be
> "Can you prove that the glibc behaviour visible to applications does not
> change"
As far as I can see,
The path that __d_path() computes can become slightly inconsistent when it
races with mount operations: it grabs the vfsmount_lock when traversing mount
points, but immediately drops it again, only to re-grab it when it reaches the
next mount point. The result is that the filename computed is not
Am Freitag, den 20.04.2007, 03:42 +0400 schrieb Manu Abraham:
> hermann pitton wrote:
> > Am Freitag, den 20.04.2007, 03:19 +0400 schrieb Manu Abraham:
> >> hermann pitton wrote:
> >>> Am Freitag, den 20.04.2007, 02:51 +0400 schrieb Manu Abraham:
> Markus Rechberger wrote:
> > On 4/20/07,
On Thursday 19 April 2007 19:35:04 Christoph Lameter wrote:
> Variable Order Page Cache Patchset
>
> This patchset modifies the core VM so that higher order page cache pages
> become possible. The higher order page cache pages are compound pages
> and can be handled in the same way as regular
On Thursday 19 April 2007 18:18, Ingo Molnar wrote:
> * Willy Tarreau <[EMAIL PROTECTED]> wrote:
> > You can certainly script it with -geometry. But it is the wrong
> > application for this matter, because you benchmark X more than
> > glxgears itself. What would be better is something like a line
Ingo Molnar wrote:
- bugfix: use constant offset factor for nice levels instead of
sched_granularity_ns. Thus nice levels work even if someone sets
sched_granularity_ns to 0. NOTE: nice support is still naive, i'll
address the many nice level related suggestions in -v4.
I have a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is preemption safe to use on PowerPC these days?
- --
Andrew J. Barr | http://www.pridelands.dyndns.org/
"Why must I fail at every attempt at masonry?"
-- Homer Simpson, "Mom and Pop Art" [AABF15]
-BEGIN PGP SIGNATURE-
Version: GnuPG
On Friday 20 April 2007 02:15, Mark Lord wrote:
> Con Kolivas wrote:
> > On Thursday 19 April 2007 23:17, Mark Lord wrote:
> >> Con Kolivas wrote:
> >> s go ahead and think up great ideas for other ways of metering out cpu
> >>
> >>> bandwidth for different purposes, but for X, given the absurd
>
On Thu, 19 Apr 2007, Greg KH wrote:
> On Thu, Apr 19, 2007 at 04:11:50PM -0700, Jesse Barnes wrote:
> > On Thursday, April 5, 2007 3:37 pm Adam Jackson wrote:
> > > So I'm attempting to do something fairly heinous (X server across
> > > five video cards), and I hit a fun bug in bridge range
On 4/19/07, Con Kolivas <[EMAIL PROTECTED]> wrote:
The cpu scheduler core is a cpu bandwidth and latency
proportionator and should be nothing more or less.
Not really. The CPU scheduler is (or ought to be) what electric
utilities call an economic dispatch mechanism -- a real-time
controller
On Thu, 19 Apr 2007 01:58:39 -0600
"Eric W. Biederman" <[EMAIL PROTECTED]> wrote:
> 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
On Thu, 19 Apr 2007 01:58:38 -0600
"Eric W. Biederman" <[EMAIL PROTECTED]> wrote:
> 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.
Chris Bergeron <[EMAIL PROTECTED]> writes:
> Hello all,
>
> Building the fglrx module against the current Linux kernel (2.6.20.7
> as of this e-mail) I'm getting an error:
>
> FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol
> 'paravirt_ops'
>
It should probably be
Con Kolivas wrote:
> You're welcome and thanks for taking the floor to speak. I would say you have
> actually agreed with me though. X is not unique, it's just an obvious so
> let's not design the cpu scheduler around the problem with X. Same goes for
> every other application. Leaving the
On 4/19/07, Alan Cox <[EMAIL PROTECTED]> wrote:
The troll is back I see.
Troll, shmoll. I call 'em like I see 'em. As much as I like and
depend on Linux, and as much as I respect the contributions and the
ideals of the EXPORT_SYMBOL_GPL partisans, they're spreading needless
FUD by spraying
On Friday 20 April 2007 01:01, Con Kolivas wrote:
> This then allows the maximum rr_interval to be as large as 5000
> milliseconds.
Just for fun, on a core2duo make allnoconfig make -j8 here are the build time
differences (on a 1000HZ config) machine:
16ms:
53.68user 4.81system 0:34.27elapsed
On Fri, 20 Apr 2007, David Chinner wrote:
> So looking at this the main thing for converting a filesystem is some extra
> bits in the mount process and replacing PAGE_CACHE_* macros with
> page_cache_*() wrapper functions.
Right.
> We can probably set all this up trivially with XFS by allowing
On Fri, 20 Apr 2007, David Chinner wrote:
> I think PAGE_CACHE_SIZE is a redundant define with these
> modifications. The page cache size in now variable and it is based
> on a multiple of PAGE_SIZE. Hence I suggest that PAGE_CACHE_SIZE and
> it's derivitives should be made to go away completely
On Fri, 20 Apr 2007, Maxim Levitsky wrote:
> First of all, today, packet writing on cd/dvd doesn't work well, it is very
> slow because
> now all file-systems are limited to 4k-barrier and cd/dvd can write only
> 32k/64k packets.
> This is why a pktcdvd was written and it emulates those 4k
David Miller <[EMAIL PROTECTED]> wrote:
>
> I applied already the patches I thought were appropriate,
> you had some crypto layer changes that you need to work
> out with Herbert Xu before the rest can be applied.
He has already fixed it by using the scatterlist interface for now.
So the last
On Thursday 19 April 2007 12:15, Mark Lord wrote:
> Con Kolivas wrote:
> > On Thursday 19 April 2007 23:17, Mark Lord wrote:
> >> Con Kolivas wrote:
> >> s go ahead and think up great ideas for other ways of metering out cpu
> >>
> >>> bandwidth for different purposes, but for X, given the absurd
David Miller <[EMAIL PROTECTED]> wrote:
>
> That file had alloc_skb_from_cache() in it, which nothing in the
> vanilla kernel ever invoked. How did it even get there? If it was
> put there for Xen's sake, that stinks because Xen is out of tree.
I think it was included because this is a list of
On Thu, 19 Apr 2007, Ed Tomlinson wrote:
> >
> > SD just doesn't do nearly as good as the stock scheduler, or CFS, here.
> >
> > I'm quite likely one of the few single-CPU/non-HT testers of this stuff.
> > If it should ever get more widely used I think we'd hear a lot more
> > complaints.
>
On 4/19/07, Lee Revell <[EMAIL PROTECTED]> wrote:
IMHO audio streamers should use SCHED_FIFO thread for time critical
work. I think it's insane to expect the scheduler to figure out that
these processes need low latency when they can just be explicit about
it. "Professional" audio software
On Thu, 19 Apr 2007 01:58:36 -0600 "Eric W. Biederman" <[EMAIL PROTECTED]>
wrote:
> This patch changes cpqphp to use kthread_run and not
> kernel_thread and daemonize to startup and setup
> the cpqphp thread.
ok.. I'll rename this to "partially convert" and shall add a note
to the changelog,
On Thursday 19 April 2007, Con Kolivas wrote:
>On Friday 20 April 2007 04:16, Gene Heskett wrote:
>> On Thursday 19 April 2007, Con Kolivas wrote:
>>
>> [and I snipped a good overview]
>>
>> >So yes go ahead and think up great ideas for other ways of metering out
>> > cpu bandwidth for different
On Thursday 19 April 2007, Con Kolivas wrote:
>On Friday 20 April 2007 04:16, Gene Heskett wrote:
>> On Thursday 19 April 2007, Con Kolivas wrote:
>>
>> [and I snipped a good overview]
>>
>> >So yes go ahead and think up great ideas for other ways of metering out
>> > cpu bandwidth for different
Have you looked at the last version (0.8)? It fixed all outstanding issues (as
far as I know).
--- Sergey Yanovich <[EMAIL PROTECTED]> wrote:
-
Hi,
The device is present in many notebooks. Notebooks depend heavily
onsuspend/resume functionality.
Hello all,
I have a [EMAIL PROTECTED] Acecad USB Tablet and I've been trying for a
while to set it up to work fine under Linux, without very much
success. I've been using the stock Debian kernel (2.6.18), but also
tried rolling my own 2.6.x git series (latest tried a 2.6.21-rc7 just
this
On Fri, Apr 20, 2007 at 10:47:57AM +1000, Con Kolivas wrote:
> On Friday 20 April 2007 01:01, Con Kolivas wrote:
> > This then allows the maximum rr_interval to be as large as 5000
> > milliseconds.
>
> Just for fun, on a core2duo make allnoconfig make -j8 here are the build time
> differences
On Thu, Apr 19, 2007 at 09:17:25AM -0400, Mark Lord wrote:
> Con Kolivas wrote:
> s go ahead and think up great ideas for other ways of metering out cpu
> >bandwidth for different purposes, but for X, given the absurd simplicity
> >of renicing, why keep fighting it? Again I reiterate that most
On Wed, 18 Apr 2007 21:08:45 +0900 Keiichi KII <[EMAIL PROTECTED]> wrote:
> +static ssize_t store_local_port(struct netconsole_target *nt, const char
> *buf,
> + size_t count)
> +{
> + spin_lock(_list_lock);
> + nt->np.local_port = simple_strtol(buf, NULL,
On Wed, 18 Apr 2007 21:06:41 +0900 Keiichi KII <[EMAIL PROTECTED]> wrote:
> From: Keiichi KII <[EMAIL PROTECTED]>
>
> This patch contains the following changes for supporting multiple logging
> agents.
>
> 1. extend netconsole to multiple netpolls
>To send kernel messages to multiple
On Thu, Apr 19, 2007 at 12:26:03PM -0700, Ray Lee wrote:
> On 4/19/07, Con Kolivas <[EMAIL PROTECTED]> wrote:
> >The one fly in the ointment for
> >linux remains X. I am still, to this moment, completely and utterly stunned
> >at why everyone is trying to find increasingly complex unique ways to
On Wed, 18 Apr 2007 21:11:14 +0900 Keiichi KII <[EMAIL PROTECTED]> wrote:
> From: Keiichi KII <[EMAIL PROTECTED]>
>
> We use symbolic link for net_device.
As Stephen said, please fully document the new interfaces in netconsole.txt.
Please also cc [EMAIL PROTECTED] on all networking-related
On Wed, 18 Apr 2007 21:14:55 +0900 Keiichi KII <[EMAIL PROTECTED]> wrote:
> From: Keiichi KII <[EMAIL PROTECTED]>
>
> We add ioctls for adding/removing target.
> If we use NETCONSOLE_ADD_TARGET ioctl,
> we can dynamically add netconsole target.
> If we use NETCONSOLE_REMOVE_TARGET ioctl,
> we
Hi again,
I recently noticed that my slub-enabled kernel won't let me stop
and restart the NFS server. It stops fine but on restart
it returns -ENOMEM.
It turns out that this is because kmem_cache_create is failing
because the name already exists in sysfs.
fs/nfsd/nfs4state creates 4
(re-added lklml)
> Patch makes available to the user the following
> thread performance statistics:
>* Involuntary Context Switches (task_struct->nivcsw)
>* Voluntary Context Switches (task_struct->nvcsw)
I suppose they might be useful, but I'd be interested in hearing what
the uses of
Max Kellermann wrote:
> On 2007/04/18 09:56, Tejun Heo <[EMAIL PROTECTED]> wrote:
>> It's more likely your chipset just has busted MSI support. Please
>> post the result of 'lspci -tv' and 'lspci -nn'.
>
> See attachments. I found the "nomsi" workaround in a forum, and
> didn't bother to
On Thu, Apr 19, 2007 at 09:35:04AM -0700, Christoph Lameter wrote:
> This patchset modifies the core VM so that higher order page cache pages
> become possible. The higher order page cache pages are compound pages
> and can be handled in the same way as regular pages.
> The order of the pages is
On 4/18/07, David Howells <[EMAIL PROTECTED]> wrote:
Aubrey Li <[EMAIL PROTECTED]> wrote:
> Here, in the attachment I wrote a small test app. Please correct if
> there is anything wrong, and feel free to improve it.
Okay... I have that working... probably. I don't know what output it's
On Fri, Apr 20, 2007 at 10:10:45AM +1000, Peter Williams wrote:
> Ingo Molnar wrote:
> >
> > - bugfix: use constant offset factor for nice levels instead of
> > sched_granularity_ns. Thus nice levels work even if someone sets
> > sched_granularity_ns to 0. NOTE: nice support is still naive,
On Wed, 18 Apr 2007 12:07:56 +0200 (CEST) Jiri Slaby <[EMAIL PROTECTED]> wrote:
> + /* non-Z with old PLX */
> + if (cinfo->num_chips != -1 && (readb(cinfo->base_addr + CyPLX_VER) &
> + 0x0f) == PLX_9050)
> + cy_writeb(cinfo->ctl_addr + 0x4c, 0);
>
On 4/19/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
Linus,
Please pull from the 'linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git
To get a one-liner fixing a host oops running non-pae guests.
Avi Kivity (1):
KVM: Fix off-by-one when writing to a nonpae guest
Adrian Bunk wrote:
> Subject: ThinkPad X60: resume no longer works (PCI related?)
> workaround: booting with "hpet=disable"
> References : http://lkml.org/lkml/2007/3/13/3
> Submitter : Dave Jones <[EMAIL PROTECTED]>
> Jeremy Fitzhardinge <[EMAIL PROTECTED]>
>
Most architectures defined three macros, MK_IOSPACE_PFN(),
GET_IOSPACE() and GET_PFN() in pgtable.h. However, the only callers
of any of these macros are in Sparc specific code, either in
arch/sparc, arch/sparc64 or drivers/sbus.
This patch removes the redundant macros from all architectures
On Thu, Apr 19, 2007 at 09:57:15PM -0700, Jeremy Fitzhardinge wrote:
> Adrian Bunk wrote:
> > Subject: ThinkPad X60: resume no longer works (PCI related?)
> > workaround: booting with "hpet=disable"
> > References : http://lkml.org/lkml/2007/3/13/3
> > Submitter : Dave
On Fri, Apr 20, 2007 at 02:52:38AM +0300, Jan Knutar wrote:
> On Thursday 19 April 2007 18:18, Ingo Molnar wrote:
> > * Willy Tarreau <[EMAIL PROTECTED]> wrote:
> > > You can certainly script it with -geometry. But it is the wrong
> > > application for this matter, because you benchmark X more
Utilized devicetree to store I2C data, ported i2c-algo-8xx.c from 2.4
approach(which remains nearly intact), refined i2c-rpx.c. I2C functionality has
been validated on
mpc885ads with EEPROM access.
Signed-off-by: Vitaly Bordug <[EMAIL PROTECTED]>
---
Jean,
The patch below may have rough edges
On Wed, 18 Apr 2007 11:13:01 +0400 Pavel Emelianov <[EMAIL PROTECTED]> wrote:
> The out_of_memory() function and SysRq-M handler call
> show_mem() to show the current memory usage state.
>
> This is also helpful to see which slabs are the largest
> in the system.
>
> Thanks Pekka for good idea
Dave Jones wrote:
> Do you have the backlight code enabled ?
> I'm guessing not.
>
Hm, think so. backlight controls work, via both
/proc/acpi/ibm/backlight and /sys/class/backlight/*/brightness.
$ ls -l /sys/class/backlight/
total 0
drwxr-xr-x 2 root root 0 Apr 19 22:13 acpi_video0
On Thu, 2007-04-19 at 09:55 -0700, Davide Libenzi wrote:
> On Thu, 19 Apr 2007, Mike Galbraith wrote:
>
> > 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
On Fri, 20 Apr 2007, Neil Brown wrote:
> Not sure how best to fix this one kmem_cache_destroy currently
> doesn't know which alias is being destroyed.
The aliases are there for decorative purposes when running without
debugging. If one switches on debugging then it matters but then the
On Thu, 19 Apr 2007 16:27:26 - "Cameron, Steve" <[EMAIL PROTECTED]> wrote:
>
> Something like
>
> if (sizeof(blah) > 4) {
>do all the assignments with shifts
> }
>
> might be slighly better since the CDB is already zeroed
> by cmd_alloc() and doesn't need to be zeroed a 2nd time.
>
>
On Thu, Apr 19, 2007 at 10:15:48PM -0700, Jeremy Fitzhardinge wrote:
> Dave Jones wrote:
> > Do you have the backlight code enabled ?
> > I'm guessing not.
> >
>
> Hm, think so. backlight controls work, via both
> /proc/acpi/ibm/backlight and /sys/class/backlight/*/brightness.
>
> $
On Fri, 2007-04-20 at 08:47 +1000, Con Kolivas wrote:
> It's those who want X to have an unfair advantage that want it to do
> something "special".
I hope you're not lumping me in with "those". If X + client had been
able to get their fair share and do so in the low latency manner they
need, I
On Thu, Apr 19, 2007 at 06:32:15PM -0700, Michael K. Edwards wrote:
> But I think SCHED_FIFO on a chain of tasks is fundamentally not the
> right way to handle low audio latency. The object with a low latency
> requirement isn't the task, it's the device. When it's starting to
> get urgent to
William Lee Irwin III wrote:
>> I'd further recommend making priority levels accessible to kernel threads
>> that are not otherwise accessible to processes, both above and below
>> user-available priority levels. Basically, if you can get SCHED_RR and
>> SCHED_FIFO to coexist as "intimate
Hello, Alan.
Alan Stern wrote:
> This doesn't solve a related problem: a subsystem wants to register
> devices and to provide a set of mutually-exclusive services to the
> devices' drivers. The mutual exclusion has to be provided by a mutex or
> something similar, and the drivers need a way to
On Thu, 19 Apr 2007, William Lee Irwin III wrote:
> Oh dear. Per-file pagesizes are foul. Better to fix up the pagecache's
> radix tree than to restrict it like this. There are other attacks on the
> multiple horizontal internal tree node allocation problem beyond
> outright B+ trees that allow
Dave Jones wrote:
> Hmm, given you hit the hpet problems and I didn't I think our X60's
> aren't quite so similar. Mine is the one with the swivelly touchscreen
> tablet-pc mode. I understand they made a regular 'laptop' X60 too,
> is that the one you have perhaps?
>
Yes, mine is a normal
On Thu, Apr 19, 2007 at 05:20:53PM -0700, Michael K. Edwards wrote:
> Embedded systems are already in 2007, and the mainline Linux scheduler
> frankly sucks on them, because it thinks it's back in the 1960's with
> a fixed supply and captive demand, pissing away "CPU bandwidth" as
> waste heat.
On Thursday April 19, [EMAIL PROTECTED] wrote:
> On Fri, 20 Apr 2007, Neil Brown wrote:
>
> > Not sure how best to fix this one kmem_cache_destroy currently
> > doesn't know which alias is being destroyed.
>
> The aliases are there for decorative purposes when running without
> debugging. If
On Fri, 20 Apr 2007, Neil Brown wrote:
> On Thursday April 19, [EMAIL PROTECTED] wrote:
> > On Fri, 20 Apr 2007, Neil Brown wrote:
> >
> > > Not sure how best to fix this one kmem_cache_destroy currently
> > > doesn't know which alias is being destroyed.
> >
> > The aliases are there for
On Thu, 19 Apr 2007 21:16:30 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Wed, 18 Apr 2007 21:14:55 +0900 Keiichi KII <[EMAIL PROTECTED]> wrote:
>
> > From: Keiichi KII <[EMAIL PROTECTED]>
> >
> > We add ioctls for adding/removing target.
> > If we use NETCONSOLE_ADD_TARGET ioctl,
> >
Another approach drop the symlinks completely. Just
write a message to the syslog informing the user that we
created an alias. If debugging is off then the user would have to consult
the syslog to find aliases.
Index: linux-2.6.21-rc6/mm/slub.c
* Jarek Poplawski <[EMAIL PROTECTED]> wrote:
> Here is my patch proposal for detecting possible lockups, when
> flush_workqueue caller holds a lock (e.g. rtnl_lock) also used in work
> functions.
looks good in principle - did you test it and it caught a bug that wasnt
caught before?
>
* Christian Hesse <[EMAIL PROTECTED]> wrote:
> I now got some error message from my system:
>
> http://www.eworm.de/tmp/cfs-suspend.jpg
ah, this pinpoints a bug: for performance reasons pick_next_task()
assumes that the runqueue is not empty - which is true for schedule(),
but not in
* Bob Picco <[EMAIL PROTECTED]> wrote:
> I had hoped to collect more data with CFS V2. It crashes in
> scale_nice_down for s2ram when attempting to disable_nonboot_cpus. So
> part of traceback looks like (typed by hand with obvious omissions):
>
> scale_nice_down
> update_stats_wait_end - not
Pine.LNX.4.64.0704181515290.25880 () alien ! or ! mcafeemobile ! com
Davide Libenzi wrote:
> On Wed, 18 Apr 2007, Ingo Molnar 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'm pretty sure the reason you cannot reproduce this warning is the line
> >
> > 1
> >
> > which can be found in param.xsl, it being a part of the docbook-xsl
> > distribution. The parameter's name is self-explanatory and a '1' suppresses
> > the version generation. I was able to get this
On Wed, Apr 18, 2007 at 10:16:54AM -0700, Randy Dunlap wrote:
> On Fri, 13 Apr 2007 11:29:43 +0200 Borislav Petkov wrote:
>
> > Sorry for the improper whitespaces, here's a correct version.
> >
> > Signed-off-by: Borislav Petkov <[EMAIL PROTECTED]>
> >
> >
> > Index: 21-rc6/scripts/kernel-doc
* 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 problems. Example: a machine
> with 100 busy httpd processes and suddenly a
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> i just tried the same and it suspended+resumed just fine:
>
> Restarting tasks ... done.
> Suspend2 debugging info:
> - Suspend core : 2.2.9.12
> - Kernel Version : 2.6.21-rc7-CFS-v3
the key difference was that i should have attempted to sw-suspend
Hi,
IMHO cancel_rearming_delayed_work is dangerous place:
- it assumes a work function always rearms (with no exception),
which probably isn't explained enough now (but anyway should
be checked in such loops);
- probably possible (theoretical) scenario: a few work
functions rearm themselves
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 threads just yet because for them there's not
> really any
Hi Len,
On Wed, 18 Apr 2007 13:42:56 -0400, Lennart Sorensen wrote:
> On Sat, Apr 14, 2007 at 07:28:07PM +0200, Jean Delvare wrote:
> > Otherwise it looks OK to me, I take the patch. If others have comments
> > or objections, just speak up and submit incremental patches as needed.
> >
> > Now I
The following patches are against 2.6.21.rc6-mm1.
Hopefully that is enough to catch most of the recent development
activity.
I am aiming to remove all kernel threads that handle signals
from user space, to remove all calls to daemonize and kernel_thread
from non-core kernel code.
kernel
On Thu, Apr 19, 2007 at 08:14:16AM +0200, Ingo Molnar wrote:
>
> * Jarek Poplawski <[EMAIL PROTECTED]> wrote:
>
> > Here is my patch proposal for detecting possible lockups, when
> > flush_workqueue caller holds a lock (e.g. rtnl_lock) also used in work
> > functions.
>
> looks good in
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]>
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
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 |
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
-
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]>
---
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
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
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]>
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
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
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
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
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]>
---
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]>
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]>
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]>
---
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
601 - 700 of 964 matches
Mail list logo
