Re: [Bugme-new] [Bug 33502] New: Caught 64-bit read from uninitialized memory in __alloc_skb

Christoph Lameter
2011-05-10T18:28:23Z

On Tue, 10 May 2011, Eric Dumazet wrote:

> > + else
> > + p = get_freepointer(s, object);
> > +
> > + local_irq_restore(flags);
> > +#else
> > + p = get_freepointer(s, object);
> > +#endif
> > + return p;
> > +}
> > +
> > static inline void set_freepointer(struct kmem_cache *s, void *object, void *fp)
> > {
> > *(void **)(object + s->offset) = fp;
> > @@ -1933,7 +1954,7 @@ redo:
> > if (unlikely(!irqsafe_cpu_cmpxchg_double(
> > s->cpu_slab->freelist, s->cpu_slab->tid,
> > object, tid,
> > - get_freepointer(s, object), next_tid(tid)))) {
> > + get_freepointer_safe(s, object), next_tid(tid)))) {
> >
> > note_cmpxchg_failure("slab_alloc", s, tid);
> > goto redo;
>
>
> Really this wont work Stephen

I am not Stephen.

> You have to disable IRQ _before_ even fetching 'object'

The object pointer is being obtained from a per cpu structure and
not from the page. What is the problem with fetching the object pointer?

> Or else, you can have an IRQ, allocate this object, pass to another cpu.

If that occurs then TID is being incremented and we will restart the loop
getting the new object pointer from the per cpu structure. The object
pointer that we were considering is irrelevant.

> This other cpu can free the object and unmap page right after you did
> the probe_kernel_address(object) (successfully), and before your cpu :
>
> p = get_freepointer(s, object); << BUG >>

If the other cpu frees the object and unmaps the page then
get_freepointer_safe() can obtain an arbitrary value since the TID was
incremented. We will restart the loop and discard the value retrieved.