linux-kernel - Re: Fwd: Problem with kernel 2.6.27.5

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>] [day] [month] [year] [list]

Message-Id: <200811161739.01179.rjw@sisk.pl>
Date:	Sun, 16 Nov 2008 17:39:00 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	"Gioacchino Mendola" <gioacchino.mendola@...il.com>
Cc:	kernel-testers@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Fwd: Problem with kernel 2.6.27.5

(General question, CCing LKML).

On Sunday, 16 of November 2008, Gioacchino Mendola wrote:
> ---------- Forwarded message ----------
> From: Gioacchino Mendola <gioacchino.mendola@...il.com>
> Date: 2008/11/16
> Subject: Problem with kernel 2.6.27.5
> To: majordomo@...r.kernel.org
> 
> 
> Hello everyone,
> This is my first mail and I hope my questions will not be too trivial!
> I'm trying to develop a  lodable kernel module but I have a problems
> with certain system functions that have been deprecated.
> With the previuos kernel(2.6.26), I used the following functions
> 
> kill_proc(pid_t pid, int sig, int priv)
> 
> find_task_by_pid(int pid)
> 
> Now i use the linux kernel 2.6.27.5
> 
> Instead of kill_proc I tried to use kill_pid.
> Kill_pid() requires as a first argument  a struct pid  and not a pid_t pid.
> 
> kill_pid(struct pid *pid, int sig, int priv)
> 
> how can I get "struct pid" by "pid_t pid"?
> 
> how can I get the "task_struct" by the pid?
> 
> Thanks in advance
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 



-- 
Everyone knows that debugging is twice as hard as writing a program
in the first place.  So if you're as clever as you can be when you write it,
how will you ever debug it? --- Brian Kernighan
--
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/