Afternoon All-
Basically, I am sending out a pseudo 'help' and bug check. I found
this thread ([BUG] threaded processes get stuck in
rt_sigsuspend/fillonedir/exit_notify) from 9/11/2000. I helping write some
software, and I think I have ran into a bug similiar to this, first, a quick
Mark Kettenis wrote:
>From: Ulrich Drepper <[EMAIL PROTECTED]>
>Date: 2000-09-13 6:35:16
>
>[EMAIL PROTECTED] writes:
>
>> I didn't realize things had changed that broke the old threading model.
>> Did Linus do more than add support for the new thread groups? I didn't
>>
From: Ulrich Drepper <[EMAIL PROTECTED]>
Date: 2000-09-13 6:35:16
[EMAIL PROTECTED] writes:
> I didn't realize things had changed that broke the old threading model.
> Did Linus do more than add support for the new thread groups? I didn't
> think any that had changed that
[EMAIL PROTECTED] writes:
> I didn't realize things had changed that broke the old threading model.
> Did Linus do more than add support for the new thread groups? I didn't
> think any that had changed that would break the old LinuxThread
> programs.
First he introduces CLONE_THREAD (or how it
[EMAIL PROTECTED] wrote:
>Date: Tue, 12 Sep 2000 07:28:22 -0700
>From: David Ford <[EMAIL PROTECTED]>
>
>Well, how about backing out the threads change until somebody is
>ready to fix everything involved. I haven't the time, depth of
>knowledge, or rep for this. At present
[EMAIL PROTECTED] wrote:
Date: Tue, 12 Sep 2000 07:28:22 -0700
From: David Ford [EMAIL PROTECTED]
Well, how about backing out the threads change until somebody is
ready to fix everything involved. I haven't the time, depth of
knowledge, or rep for this. At present the only
[EMAIL PROTECTED] writes:
I didn't realize things had changed that broke the old threading model.
Did Linus do more than add support for the new thread groups? I didn't
think any that had changed that would break the old LinuxThread
programs.
First he introduces CLONE_THREAD (or how it was
Mark Kettenis wrote:
From: Ulrich Drepper [EMAIL PROTECTED]
Date: 2000-09-13 6:35:16
[EMAIL PROTECTED] writes:
I didn't realize things had changed that broke the old threading model.
Did Linus do more than add support for the new thread groups? I didn't
think any
Theodore Y. Ts'o wrote:
>> I've told Linus several times about this problems but he puts out one
>> test release after the other without this fixed.
>
>This is kinda important, I run DNS tools which are threaded amongst
>numerous other threaded programs a lot. What needs to be
"Theodore Y. Ts'o" wrote:
>Date:Mon, 11 Sep 2000 18:27:30 -0700
>From: David Ford <[EMAIL PROTECTED]>
>
>> I've told Linus several times about this problems but he puts out one
>> test release after the other without this fixed.
>
>This is kinda important, I run DNS
Date:Mon, 11 Sep 2000 18:27:30 -0700
From: David Ford <[EMAIL PROTECTED]>
> I've told Linus several times about this problems but he puts out one
> test release after the other without this fixed.
This is kinda important, I run DNS tools which are threaded amongst
Date:Mon, 11 Sep 2000 18:27:30 -0700
From: David Ford [EMAIL PROTECTED]
I've told Linus several times about this problems but he puts out one
test release after the other without this fixed.
This is kinda important, I run DNS tools which are threaded amongst
numerous
Theodore Y. Ts'o wrote:
I've told Linus several times about this problems but he puts out one
test release after the other without this fixed.
This is kinda important, I run DNS tools which are threaded amongst
numerous other threaded programs a lot. What needs to be done to
David Ford <[EMAIL PROTECTED]> writes:
> Regardless of who does it or whether or not it goes in testX patch, I'd
> surely like to have a patch(es) for my systems. Depending on what gets run,
> I could easily end up with hundreds+ of hung programs and zombies.
This is completely unrelated. The
Ulrich Drepper wrote:
> Ray Bryant <[EMAIL PROTECTED]> writes:
>
> > Is there a succinct description of the the thread group changes
> > someplace? I'd be willing to take a look at fixing linuxthreads,
> > but haven't seen any description (other than the kernel source) of
> > what the changes
Ulrich Drepper wrote:
> David Ford <[EMAIL PROTECTED]> writes:
>
> > On the recent test kernels, processes get stuck. A kill -9 results in
> > zombies.
>
> The thread group changes broke the signal handling in linuxthreads.
> The CLONE_SIGHAND is now also used to enable thread groups but since
Ray Bryant <[EMAIL PROTECTED]> writes:
> Is there a succinct description of the the thread group changes
> someplace? I'd be willing to take a look at fixing linuxthreads,
> but haven't seen any description (other than the kernel source) of
> what the changes are. Or is someone already working
Is there a succinct description of the the thread group changes someplace?
I'd be willing to take a look at fixing linuxthreads, but haven't seen any
description
(other than the kernel source) of what the changes are. Or is someone already
working on this?
Ulrich Drepper wrote:
>
> The thread
David Ford <[EMAIL PROTECTED]> writes:
> On the recent test kernels, processes get stuck. A kill -9 results in
> zombies.
The thread group changes broke the signal handling in linuxthreads.
The CLONE_SIGHAND is now also used to enable thread groups but since
linuxthreads already used
On the recent test kernels, processes get stuck. A kill -9 results in
zombies.
# cat /tmp/ps.out
PID USER STAT WCHAN COMMAND
1 root Sfillon init [5]
2 root SW acpi_i [kapmd]
3 root SW swap_o [kswapd]
4 root SW brw_pa [kflushd]
5 root SW
On the recent test kernels, processes get stuck. A kill -9 results in
zombies.
# cat /tmp/ps.out
PID USER STAT WCHAN COMMAND
1 root Sfillon init [5]
2 root SW acpi_i [kapmd]
3 root SW swap_o [kswapd]
4 root SW brw_pa [kflushd]
5 root SW
Is there a succinct description of the the thread group changes someplace?
I'd be willing to take a look at fixing linuxthreads, but haven't seen any
description
(other than the kernel source) of what the changes are. Or is someone already
working on this?
Ulrich Drepper wrote:
The thread
Ray Bryant [EMAIL PROTECTED] writes:
Is there a succinct description of the the thread group changes
someplace? I'd be willing to take a look at fixing linuxthreads,
but haven't seen any description (other than the kernel source) of
what the changes are. Or is someone already working on
Ulrich Drepper wrote:
David Ford [EMAIL PROTECTED] writes:
On the recent test kernels, processes get stuck. A kill -9 results in
zombies.
The thread group changes broke the signal handling in linuxthreads.
The CLONE_SIGHAND is now also used to enable thread groups but since
24 matches
Mail list logo
