Messages in this thread | | | Date | Mon, 10 Mar 2014 21:24:55 -0400 | From | Dave Jones <> | Subject | Re: oops in slab/leaks_show |
| |
On Tue, Mar 11, 2014 at 10:01:35AM +0900, Joonsoo Kim wrote: > On Tue, Mar 11, 2014 at 09:35:00AM +0900, Joonsoo Kim wrote: > > On Fri, Mar 07, 2014 at 11:18:30AM -0600, Christoph Lameter wrote: > > > Joonsoo recently changed the handling of the freelist in SLAB. CCing him. > > > > > > > I pretty much always use SLUB for my fuzzing boxes, but thought I'd give SLAB a try > > > > for a change.. It blew up when something tried to read /proc/slab_allocators > > > > (Just cat it, and you should see the oops below) > > > > Hello, Dave. > > > > Today, I did a test on v3.13 which contains all my changes on the handling of > > the freelist in SLAB and couldn't trigger oops by just 'cat /proc/slab_allocators'. > > > > So I look at the code and find that there is race window if there is multiple users > > doing 'cat /proc/slab_allocators'. Did your test do that? > > Opps, sorry. I am misunderstanding something. Maybe there is no race. > Anyway, How do you test it?
1. build kernel with CONFIG_SLAB=y. 2. boot kernel 3. cat /proc/slab_allocators
that's it.
Dave
| |