On Thu, 28 Jun 2007, David Miller wrote:
> From: Andrew Morton <[email protected]>
> Date: Thu, 28 Jun 2007 22:24:24 -0700
>
> > So what happens when two quite different threads of control are doing
> > IO against two hunks of kmalloced memory which happen to come from the same
> > page? Either some (kernel-wide) locking is needed, or that pageframe needs
> > to be treated as readonly?
>
> Or you put an atomic_t at the beginning or tail of every SLAB
> object. It's a space cost not a runtime cost for the common
> case which is:
Hmmm... We could do something like
kmem_cache_get(slab, object)
and
kmem_cache_put(slab, object)
kmem_cache_get would disable allocations from the slab and increment a
refcount.
kmem_cache_put would enable allocations again if the refcount reaches
one.
The problem is that freeing an object may cause writes to the object. F.e.
poisoning will overwrite the object on free. SLUB will put its free
pointer in the first words etc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
