Functions inside kernel modules that use __ref
will end up being placed in .ARM.exidx.ref.text
section by gcc.
Currently we don't consider adding these functions
to arm unwind tables.
Hence, if we turn slub debug on by default we end up
with the messages of this sort:
unwind: Index not found
Functions inside kernel modules that use __ref
will end up being placed in .ARM.exidx.ref.text
section by gcc.
Currently we don't consider adding these functions
to arm unwind tables.
Hence, if we turn slub debug on by default we end up
with the messages of this sort:
unwind: Index not found
On Wed, Jun 10, 2015 at 12:25:54PM -, vigne...@codeaurora.org wrote:
> Gentle reminder for review comments.
I don't see anything wrong with the patch... but it needs to find its
way into the patch system to be applied, so it doesn't get forgotten.
Please add it there along with Laura's
Gentle reminder for review comments.
> Forgot to add Maintainers. Adding them now.
>
>> On 05/13/2015 08:20 AM, Vignesh Radhakrishnan wrote:
>>> Functions inside kernel modules that use __ref
>>> will end up being placed in .ARM.exidx.ref.text
>>> section by gcc.
>>>
>>> Currently we don't
Gentle reminder for review comments.
Forgot to add Maintainers. Adding them now.
On 05/13/2015 08:20 AM, Vignesh Radhakrishnan wrote:
Functions inside kernel modules that use __ref
will end up being placed in .ARM.exidx.ref.text
section by gcc.
Currently we don't consider adding these
On Wed, Jun 10, 2015 at 12:25:54PM -, vigne...@codeaurora.org wrote:
Gentle reminder for review comments.
I don't see anything wrong with the patch... but it needs to find its
way into the patch system to be applied, so it doesn't get forgotten.
Please add it there along with Laura's
Forgot to add Maintainers. Adding them now.
> On 05/13/2015 08:20 AM, Vignesh Radhakrishnan wrote:
>> Functions inside kernel modules that use __ref
>> will end up being placed in .ARM.exidx.ref.text
>> section by gcc.
>>
>> Currently we don't consider adding these functions
>> to arm unwind
Forgot to add Maintainers. Adding them now.
On 05/13/2015 08:20 AM, Vignesh Radhakrishnan wrote:
Functions inside kernel modules that use __ref
will end up being placed in .ARM.exidx.ref.text
section by gcc.
Currently we don't consider adding these functions
to arm unwind tables.
Hence,
On 05/13/2015 08:20 AM, Vignesh Radhakrishnan wrote:
Functions inside kernel modules that use __ref
will end up being placed in .ARM.exidx.ref.text
section by gcc.
Currently we don't consider adding these functions
to arm unwind tables.
Hence, if we turn slub debug on by default we end up
with
On 05/13/2015 08:20 AM, Vignesh Radhakrishnan wrote:
Functions inside kernel modules that use __ref
will end up being placed in .ARM.exidx.ref.text
section by gcc.
Currently we don't consider adding these functions
to arm unwind tables.
Hence, if we turn slub debug on by default we end up
with
Functions inside kernel modules that use __ref
will end up being placed in .ARM.exidx.ref.text
section by gcc.
Currently we don't consider adding these functions
to arm unwind tables.
Hence, if we turn slub debug on by default we end up
with the messages of this sort:
unwind: Index not
Functions inside kernel modules that use __ref
will end up being placed in .ARM.exidx.ref.text
section by gcc.
Currently we don't consider adding these functions
to arm unwind tables.
Hence, if we turn slub debug on by default we end up
with the messages of this sort:
unwind: Index not
12 matches
Mail list logo
