linux-kernel - Re: [stable] [PATCH 1/2] posix-timers: fix RLIMIT

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, 31 Mar 2009 16:57:50 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Chris Wright <chrisw@...s-sol.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <peterz@...radead.org>,
	Peter Lojkin <ia6432@...ox.ru>, linux-kernel@...r.kernel.org,
	Roland McGrath <roland@...hat.com>, stable@...nel.org
Subject: Re: [stable] [PATCH 1/2] posix-timers: fix RLIMIT_CPU && fork()

On 03/31, Chris Wright wrote:
>
> * Oleg Nesterov (oleg@...hat.com) wrote:
> > See http://bugzilla.kernel.org/show_bug.cgi?id=12911
> >
> > copy_signal() copies signal->rlim, but RLIMIT_CPU is "lost". Because
> > posix_cpu_timers_init_group() sets cputime_expires.prof_exp = 0 and thus
> > fastpath_timer_check() returns false unless we have other expired cpu timers.
> >
> > Change copy_signal() to set cputime_expires.prof_exp if we have RLIMIT_CPU.
> > Also, set cputimer.running = 1 in that case. This is not strictly necessary,
> > but imho makes sense.
>
> For -stable should this be instead of 37bebc70d7ad4144c571d74500db3bb26ec0c0eb?

Yes, sorry for confusion.

The commit above was targeted for 2.6.29, it is not optimal. When/if
"[PATCH 1/2] posix-timers: fix RLIMIT_CPU && fork()" will be merged, I'll sent
the "revert" patch.

see http://marc.info/?t=123783777600004

Oleg.

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