Re: 4.13 regression: get_kctl_0dB_offset doesn't handle all possible callbacks

2017-10-16 Thread Takashi Iwai
On Sat, 14 Oct 2017 07:31:20 +0200, Takashi Sakamoto wrote: > > Hi, > > On Oct 14 2017 07:46, PaX Team wrote: > > what KERNEXEC on i386 does is that it executes kernel code in its own > > 0-based > > code segment hence the 'low' code addresses. due to the current logic that > > checks for SNDRV_

Re: 4.13 regression: get_kctl_0dB_offset doesn't handle all possible callbacks

2017-10-13 Thread Takashi Sakamoto
Hi, On Oct 14 2017 07:46, PaX Team wrote: > what KERNEXEC on i386 does is that it executes kernel code in its own 0-based > code segment hence the 'low' code addresses. due to the current logic that > checks for SNDRV_CTL_ELEM_ACCESS_TLV_CALLBACK in get_kctl_0dB_offset, this > callback address is

4.13 regression: get_kctl_0dB_offset doesn't handle all possible callbacks

2017-10-13 Thread PaX Team
hello devs, upstream commit 99b5c5bb9a5435a5ae5d46445ac0f2bf6aa5ee52 removed the use of set_fs in get_kctl_0dB_offset under the assumption that the only runtime value of kctl->tlv.c was snd_hda_mixer_amp_tlv. alas, recently, the KERNEXEC and UDEREF features in PaX reported a violation of this assu