linux-kernel - Re: [PATCH 3/4] Clean up the kill_someting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 3 Feb 2008 16:28:20 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Pavel Emelyanov <xemul@...nvz.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	devel@...nvz.org, Oleg Nesterov <oleg@...sign.ru>
Subject: Re: [PATCH 3/4] Clean up the kill_someting_info

On Mon, 28 Jan 2008 18:16:35 +0300 Pavel Emelyanov <xemul@...nvz.org> wrote:

> This is the first stop (of two) in removing the kill_pgrp_info.
> 
> All the users of this function are in kernel/signal.c, but all
> they need is to call __kill_pgrp_info() with the tasklist_lock
> read-locked.
> 
> Fortunately, one of its users is the kill_something_info(),
> which already needs this lock in one of its branches, so clean
> these branches up and call the __kill_pgrp_info() directly.
> 
> Based on Oleg's view of how this function should look.

This patch causes my Fedora Core 3 x86_64 machine to fail.  When
rc.sys_init runs /sbin/start_udev a segmentation fault in start_udev is
reported and no device nodes are created.  This is the only one of my test
machines which behaves this way.

Config: http://userweb.kernel.org/~akpm/config-x.txt
Running udev-039-8.FC3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/