by insert/remove "-mfentry")
without doing a "make clean", then recordmcount will omit some calls.
Those restrictions are easy to guess, and recovery is easy. Therefore,
Ack'ed by: John Reiser
--
--
To unsubscribe from this list: send the line "unsubscrib
Andi Kleen wrote:
> On Thu, Jan 10, 2008 at 04:59:52PM -0800, John Reiser wrote:
>
>>Andi Kleen wrote:
>>
>>>But actually checking the default implementation in linkage.h already
>>>implements size: [snip]
>>
>>>Are you sure it doesn't
comment
in linkage.h which explains one motivation. PowerPC is different
("_GLOBAL" instead of "ENTRY") and foreign to me, so I left it alone.
Signed off by: John Reiser <[EMAIL PROTECTED]>
diff --git a/include/linux/linkage.h b/include/linux/linkage.h
index ff203dd..024cf
fast path to 'ret' is in the middle, and code for the slow
path appears after the 'ret'; or when a recursive tail 'falls
through" into the entry point.
A quick test shows that multiple .size pseudo-ops for the same symbol
are accepted (the last one wins) so defaul
2008-01-07 08:45:39.0 -0800
@@ -6,6 +6,7 @@
*/
.globl csum_partial
+ .type csum_partial, @function
csum_partial:
;; r10 - src
@@ -109,3 +110,4 @@
addu.b [$r10],$r12
ret
move.d $r12,$r10
+ .size csum_partial, . - csum_partial
ind(memcheck) to record correctly
the state of the object. Is the object initialized (and which parts
of it, and were the initializations performed into allocated space),
or is it merely allocated and uninitialized?
--
John Reiser, [EMAIL PROTECTED]
--
To unsubscribe from this list: send
Theodore Tso wrote:
> On Fri, Dec 14, 2007 at 04:30:08PM -0800, John Reiser wrote:
>
>>There is a path that goes from user data into the pool.
Note particularly that the path includes data from other users.
Under the current implementation, anyone who accesses /dev/urandom
is subje
heck_after(cachep, flags, objp, caller);
if (objp && cachep->ctor)
cachep->ctor(objp, cachep, 0);
/* checker notes initializations during ctor [above] */
--
John Reiser, [EMAIL PROTECTED]
--
To unsubscribe from this list: send the line "unsubscribe l
Theodore Tso wrote:
> On Fri, Dec 14, 2007 at 12:45:23PM -0800, John Reiser wrote:
>
>>>It's getting folded into the random number pool, where it will be
>>>impossible to recover it unless you already know what was in the
>>>pool. And if you know what
es, 0, -bytes & 3);
add_entropy_words(r, tmp, (bytes + 3) / 4);
credit_entropy_store(r, bytes*8);
}
--
John Reiser, [EMAIL PROTECTED]
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
p;tmp[0];
+ __u8 *dst = bytes + src;
+ for (; 0!=(3 & bytes); ++bytes)
+ *dst++ = *src++;
+ }
+ add_entropy_words(r, tmp, bytes>>2);
credit_entropy_store(r, bytes*8);
}
--
John Reiser,
Chuck Ebbert wrote:
> John Reiser wrote:
>
>>The value of ->sysenter_return is interpreted in user space by the
>>sysexit instruction; nobody else cares what the value is. The kernel
>>is not required to provide a good value when vdso_enabled is zero,
>>be
the reason is some magic in glibc.
In the past there were problems where user code could not single-step
(or even read the code of) such system calls. Can these two operations
be performed today with what you propose, particularly if FIX_VDSO is
near 0xf000 ?
--
John Reiser, [EMAIL PROTECTED]
Oleg Nesterov wrote:
> John Reiser wrote:
>>+ switch (vdso_enabled) {
>>+ case 0: /* none */
>>+ return 0;
>
>
> This means we don't initialize mm->context.vdso and ->sysenter_return.
>
> Is it ok? For example, setup_
and also 207020 and 162797.
Signed-off-by: John Reiser <[EMAIL PROTECTED]>
diff --git a/arch/i386/kernel/sysenter.c b/arch/i386/kernel/sysenter.c
index 13ca54a..f8c4d76 100644
--- a/arch/i386/kernel/sysenter.c
+++ b/arch/i386/kernel/sysenter.c
@@ -22,6 +22,8 @@
#include
#include
#i
0x90090034
# which is too big by 0x08048000 [p_vaddr of first PT_LOAD]
# because the correct value is 0x88048034.
# Note that AT_ENTRY at 0xbacc is 0x88048114 which is correct.
--
John Reiser, [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-ker
cording to
the other license.
[I am not subscribed to this mailing list, so CC: or mail me if appropriate.]
--
John Reiser, [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
e (GPLv2) and pre-compiled binary for x86 are available.
[I'm not subscribed to this mailing list, so CC: or mail me if appropriate.]
--
John Reiser, [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTE
18 matches
Mail list logo
