Hrm, I've got a lurking suspicion that this issue has a timing component
(and that could actually be why it works in 3.0, not that it's really
fixed but that the timing that some change in timing makes the problem
much harder to trigger). If your CPU is being pegged then that could be
affecting the results.
We'll mark this one as good for now, but if the bisect goes bad we may
come back to this point.
Third build (bisect002) is now available.
# bad: [a09ed5e00084448453c8bada4dcd31e5fbfc2f21] vmscan: change shrink_slab() interfaces by passing shrink_control
git bisect bad a09ed5e00084448453c8bada4dcd31e5fbfc2f21
Hrm, I've got a lurking suspicion that this issue has a timing component
(and that could actually be why it works in 3.0, not that it's really
fixed but that the timing that some change in timing makes the problem
much harder to trigger). If your CPU is being pegged then that could be
affecting the results.
We'll mark this one as good for now, but if the bisect goes bad we may
come back to this point.
Third build (bisect002) is now available.
# bad: [a09ed5e0008444 8453c8bada4dcd3 1e5fbfc2f21] vmscan: change shrink_slab() interfaces by passing shrink_control 453c8bada4dcd31 e5fbfc2f21
git bisect bad a09ed5e00084448