Sure.
On Thu, Jul 5, 2018 at 12:08 PM, Laura Abbott wrote:
> On 07/05/2018 08:58 AM, Andy Lutomirski wrote:
>>
>> On Tue, Jul 3, 2018 at 4:34 PM, Laura Abbott wrote:
>>>
>>>
>>> The vDSO needs to have a unique build id in a similar manner
>>> to the kernel and modules. Use the build salt macro.
On 07/05/2018 08:58 AM, Andy Lutomirski wrote:
On Tue, Jul 3, 2018 at 4:34 PM, Laura Abbott wrote:
The vDSO needs to have a unique build id in a similar manner
to the kernel and modules. Use the build salt macro.
Looks good to me. I have no idea whose tree these would go through.
I was
On Tue, Jul 3, 2018 at 4:34 PM, Laura Abbott wrote:
>
> The vDSO needs to have a unique build id in a similar manner
> to the kernel and modules. Use the build salt macro.
>
Looks good to me. I have no idea whose tree these would go through.
> Signed-off-by: Laura Abbott
> ---
> v5: Switched t
The vDSO needs to have a unique build id in a similar manner
to the kernel and modules. Use the build salt macro.
Signed-off-by: Laura Abbott
---
v5: Switched to using the single line BUILD_SALT macro
---
arch/x86/entry/vdso/vdso-note.S | 3 +++
arch/x86/entry/vdso/vdso32/note.S | 3 +++
2 f
