On 01/18/2017 06:19 PM, Andy Lutomirski wrote:
> On Wed, Jan 18, 2017 at 2:16 PM, David Smith wrote:
>> On 01/16/2017 03:14 PM, Thomas Gleixner wrote:
>>> On Mon, 16 Jan 2017, David Smith wrote:
... stuff deleted ...
>>>> If you put that new access_ok() call in
On 01/16/2017 03:14 PM, Thomas Gleixner wrote:
> On Mon, 16 Jan 2017, David Smith wrote:
>
>> If you call access_ok() with page faulting disabled, you'll still see
>> this new warning.
>
> And how so? It's just checking for task context. page fault disable/ena
If you call access_ok() with page faulting disabled, you'll still see this new
warning. If you put that new access_ok() call in a module that gets
loaded/unloaded, you see one warning for every module load, which gets a bit
annoying.
How about modifying it like this:
---
From: David
active
+ exception handling becomes completely broken in programs
instrumented by the current version of dyninst (PR14702)
+ command line interrupts are slightly mishandled (PR15049)
+ not all registers are made available on 32-bit x86 (PR15136)
See dyninst/README and the systemtap/dyninst B
t; >
> > > I'm not sure if we want to use variable-size array on stack. What
> > > hacks are you doing with max_t/max?
> > >
> > > Pavel
> >
> > Hi Pavel,
> >
> > Here's an alternate solution from David, signoffs pending --
> >
> &g
Mathieu Desnoyers wrote:
> Hrm, what would happen if a gcc optimization eventually decides to mix
> the memory layout of the strings ? Is there something that specifies
> that they won't ?
Here's another patch that Roland wrote and I tested that
attempts to solve the potential problem of string or
Mathieu Desnoyers wrote:
> * David Smith ([EMAIL PROTECTED]) wrote:
>> Mathieu Desnoyers wrote:
>>> * Roland McGrath ([EMAIL PROTECTED]) wrote:
>>>>> If we want to do it safely, I think we should iterate from
>>>>> __start___markers to __stop___marke
Mathieu Desnoyers wrote:
> * Roland McGrath ([EMAIL PROTECTED]) wrote:
>>> If we want to do it safely, I think we should iterate from
>>> __start___markers to __stop___markers symbols of vmlinux and get the
>>> pointers to the name/format string pairs.
>>>
>>> The same can then be done with modules
ll available markers in a kernel? Note that
I also have a requirement to get a list of all available markers in a
kernel that isn't the currently running one.
--
David Smith
[EMAIL PROTECTED]
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
-
To unsubscribe from
> Can the folks who are seeing crashes running athlon optimised kernels all
> mail me
> - CPU model/stepping
vendor_id : AuthenticAMD
cpu family : 6
model : 4
model name : AMD Athlon(tm) Processor
stepping: 2
cpu MHz : 902.064
thunderbird 900 (200 MHz FSB
10 matches
Mail list logo
