linux-kernel - Re: [resend][PATCH 3/4] move cred_guard_mutex from task_struct to signal

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:	Tue, 26 Oct 2010 22:04:50 +0900 (JST)
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	Roland McGrath <roland@...hat.com>
Cc:	kosaki.motohiro@...fujitsu.com, Oleg Nesterov <oleg@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-mm <linux-mm@...ck.org>
Subject: Re: [resend][PATCH 3/4] move cred_guard_mutex from task_struct to signal_struct

Hello,

> > Except: I am not sure about -stable. At least, this patch should
> > not go into the <2.6.35 kernels, it relies on misc changes which
> > changed the scope of task->signal. Before 2.6.35 almost any user
> > of ->cred_guard_mutex can race with exit and hit ->signal == NULL.
> 
> I see no justification for a change like this in any -stable tree.  It's
> just a cleanup, right?  If it's a prerequisite for the fix we like for an
> "important" bug, then that's a different story.  In its own right, it's
> clearly not appropriate for backporting.

Because [4/4] depend on [3/4] and I hope to backport it. Do you dislike it
too?


Thanks.



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