linux-kernel - Re: [PATCH] x86 ptrace: fix PTRACE

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]

Message-Id: <20080701093212.6D9DA15420E@magilla.localdomain>
Date:	Tue,  1 Jul 2008 02:32:12 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
	stable@...nel.org, TAKADA Yoshihito <takada@....nifty.com>
Subject: Re: [PATCH] x86 ptrace: fix PTRACE_GETFPXREGS error

> since the original fix is already upstream, i've applied the delta patch 
> below. Should we still do this for v2.6.26 or can we defer it to 
> v2.6.27? As ptrace is the only user of this facility for now this would 
> be an identity transformation AFAICS and the v2.6.26 release is very 
> close.

I don't think there's a problem with 2.6.26 either way.  I agree that the
user_regset internal API does not matter much before 2.6.27.

My patch alone applies to 2.6.25, which is why I CC'd it to stable.
I think applying that (and not takada's patch) to stable-2.6.25
would be best.


Thanks,
Roland
--
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/