summaryrefslogtreecommitdiff
path: root/lib/xz
diff options
context:
space:
mode:
authorAnton Blanchard <anton@samba.org>2012-09-03 16:48:46 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-09-14 10:00:22 -0700
commit59d0622a07571c6344f0e3c71e7a1a71eb8db9e9 (patch)
treeb7e27ef692a8a19da9d42d60cd4301394fc8c3bb /lib/xz
parent652f43702b224351b790fd9182744d7946d4cdf6 (diff)
downloadlwn-59d0622a07571c6344f0e3c71e7a1a71eb8db9e9.tar.gz
lwn-59d0622a07571c6344f0e3c71e7a1a71eb8db9e9.zip
powerpc: Keep thread.dscr and thread.dscr_inherit in sync
commit 00ca0de02f80924dfff6b4f630e1dff3db005e35 upstream. When we update the DSCR either via emulation of mtspr(DSCR) or via a change to dscr_default in sysfs we don't update thread.dscr. We will eventually update it at context switch time but there is a period where thread.dscr is incorrect. If we fork at this point we will copy the old value of thread.dscr into the child. To avoid this, always keep thread.dscr in sync with reality. This issue was found with the following testcase: http://ozlabs.org/~anton/junkcode/dscr_inherit_test.c Signed-off-by: Anton Blanchard <anton@samba.org> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'lib/xz')
0 files changed, 0 insertions, 0 deletions