linux-kernel - Re: [PATCH] rlim in proc/<pid>/status (2nd rev.)

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

Date:	Wed, 16 Jan 2008 16:33:12 +0900
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	Clifford Wolf <clifford@...fford.at>
Cc:	kosaki.motohiro@...fujitsu.com, serge@...lyn.com,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] rlim in proc/<pid>/status (2nd rev.)

Hi Clifford,

> +static inline char *task_rlim(struct task_struct *p, char *buffer)
> +{
> +	unsigned long flags;
> +	struct rlimit rlim[RLIM_NLIMITS];
> +	int i;
> +	
> +	rcu_read_lock();
> +	if (lock_task_sighand(p, &flags)) {
> +		for (i=0; i<RLIM_NLIMITS; i++)
> +			rlim[i] = p->signal->rlim[i];
> +		unlock_task_sighand(p, &flags);
> +	}

lock_task_sighand is possible return NULL?
if so, rlim is uninitialized when NULL.


- kosaki


--
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/