From: Jiri Slaby <jirislaby@gmail.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
ebiederm@xmission.com, roland@redhat.com,
linux-kernel@vger.kernel.org, Matthew Wilcox <matthew@wil.cx>
Subject: Re: [PATCH 1/1] signal: make group kill signal fatal
Date: Mon, 25 May 2009 18:21:55 +0200 [thread overview]
Message-ID: <4A1AC5A3.9000600@gmail.com> (raw)
In-Reply-To: <20090525000750.GA2301@redhat.com>
On 05/25/2009 02:07 AM, Oleg Nesterov wrote:
> On 05/24, Jiri Slaby wrote:
>>
>> __fatal_signal_pending() returns now true only for a non-group sent
>> sigkill, i. e. for example tgkill, send_sig...
>
> No. Please look at complete_signal(). If we queue a fatal signal,
> we always add SIGKILL to any thread.
Ah, thanks. But it looks like it doesn't work well in some cases.
Consider this kernel code:
#include <linux/fs.h>
#include <linux/miscdevice.h>
#include <linux/module.h>
#include <linux/poll.h>
#include <linux/sched.h>
static int release(struct inode *ino, struct file *file)
{
unsigned int a;
printk(KERN_DEBUG "fst\n");
for (a = 0; a < 10; a++) {
printk(KERN_DEBUG "%s: SP=%u FSP=%u pend=%.16lx
shpend=%.16lx\n",
__func__,
signal_pending(current),
fatal_signal_pending(current),
current->pending.signal.sig[0],
current->signal->shared_pending.signal.sig[0]);
if (fatal_signal_pending(current))
break;
msleep(1000);
}
printk(KERN_DEBUG "done\n");
return 0;
}
static DECLARE_WAIT_QUEUE_HEAD(wq);
static unsigned int poll(struct file *file, struct poll_table_struct *p)
{
poll_wait(file, &wq, p);
return 0;
}
static const struct file_operations fops = {
.owner = THIS_MODULE,
.release = release,
.poll = poll,
};
static struct miscdevice m = {
.minor = MISC_DYNAMIC_MINOR,
.name = "m",
.fops = &fops,
};
static int init1(void)
{
return misc_register(&m);
}
static void exit1(void)
{
misc_deregister(&m);
}
module_init(init1);
module_exit(exit1);
MODULE_LICENSE("GPL");
----------------------------------------------
And this user code:
#include <err.h>
#include <fcntl.h>
#include <poll.h>
#include <stdio.h>
#include <unistd.h>
#include <sys/stat.h>
#include <sys/types.h>
#include <sys/wait.h>
int main(int argc, char **argv)
{
struct pollfd fds = { .events = POLLIN };
int fd;
fd = open("/dev/m", O_RDONLY);
if (fd < 0)
err(1, "open");
fds.fd = fd;
if (poll(&fds, 1, -1) < 0)
err(2, "poll");
close(fd);
return 0;
}
----------------------------------------------
It outputs:
fst
release: SP=1 FSP=0 pend=0000000000000000 shpend=0000000000000100
release: SP=1 FSP=0 pend=0000000000000000 shpend=0000000000000100
release: SP=1 FSP=0 pend=0000000000000000 shpend=0000000000000100
release: SP=1 FSP=0 pend=0000000000000000 shpend=0000000000000100
release: SP=1 FSP=0 pend=0000000000000000 shpend=0000000000000100
release: SP=1 FSP=0 pend=0000000000000000 shpend=0000000000000100
release: SP=1 FSP=0 pend=0000000000000000 shpend=0000000000000100
release: SP=1 FSP=0 pend=0000000000000000 shpend=0000000000000100
release: SP=1 FSP=0 pend=0000000000000000 shpend=0000000000000100
release: SP=1 FSP=0 pend=0000000000000000 shpend=0000000000000100
done
I.e. it won't get propagated to current->pending. Don't you have idea
why? If the poll isn't there, it works well.
glibc 2.9, x86_64
next prev parent reply other threads:[~2009-05-25 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 20:47 [PATCH 1/1] signal: make group kill signal fatal Jiri Slaby
2009-05-25 0:07 ` Oleg Nesterov
2009-05-25 16:21 ` Jiri Slaby [this message]
2009-05-25 17:20 ` Oleg Nesterov
2009-05-25 18:15 ` Jiri Slaby
2009-05-25 22:51 ` Oleg Nesterov
2009-06-02 12:54 ` Jiri Slaby
2009-06-02 14:50 ` Oleg Nesterov
2009-06-03 1:52 ` Roland McGrath
2009-06-04 2:27 ` Oleg Nesterov
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=4A1AC5A3.9000600@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=oleg@redhat.com \
--cc=roland@redhat.com \
/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