From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOps in exec_usermodehelper
Date: Tue, 28 Nov 2000 18:59:54 MET-1 [thread overview]
Message-ID: <E29780A2645@vcnet.vc.cvut.cz> (raw)
On 29 Nov 00 at 1:53, Andrew Morton wrote:
> hmm.. Quite a few things fixed here.
>
> Could you please test this patch? It's against 2.4.0-test12-pre2,
> should be OK against test11.
I upgraded to 12-pre2 already ;-) It looks like that it works.
> - keventd is now capable of reaping dead children. I will be all ears
> if someone can tell me how to get a kernel thread to accept signals
> without having to install a handler with
>
> sa.sa_handler = (__sighandler_t)100;
Is there any reason why not set sa.sa_handler to SIG_IGN? According
to arch/i386/kernel/signal.c:do_signal(), signal manpage and my memory,
kernel does automatic child reaping in such configuration. So you
could even remove waitpid() loop from keventd. I did not tried it yet,
but it looks like obvious solution...
BTW, are you sure that kernel does not try to deliver SIGSEGV to
keventd() when signal arrives. It looks like that it should, but it
probably fails somewhere during way due to non-existent userspace for
this process.
> + sa.sa.sa_handler = (__sighandler_t)100; /* Surely there's a better way? */
> + sa.sa.sa_flags = 0;
SA_RESTART? SA_NOCLDSTOP ?
> + do_sigaction(SIGCHLD, &sa, (struct k_sigaction *)0);
>
> for (;;) {
> - current->state = TASK_INTERRUPTIBLE;
> + __set_task_state(curtask, TASK_INTERRUPTIBLE);
> add_wait_queue(&context_task_wq, &wait);
>
> /*
> @@ -46,15 +59,19 @@
> schedule();
>
> remove_wait_queue(&context_task_wq, &wait);
> - current->state = TASK_RUNNING;
> + __set_task_state(curtask, TASK_RUNNING);
> run_task_queue(&tq_context);
> + if (signal_pending(curtask)) {
> + while (waitpid(-1, (unsigned int *)0, __WALL|WNOHANG) > 0)
> + ;
> + flush_signals(curtask);
> + recalc_sigpending(curtask);
> + }
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-28 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-28 18:59 Petr Vandrovec [this message]
2000-11-29 7:19 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2000-11-27 14:11 Petr Vandrovec
2000-11-28 0:47 ` Andrew Morton
2000-11-28 14:53 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E29780A2645@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®