Messages in this thread | | | From | Linus Torvalds <> | Date | Wed, 3 Nov 2010 13:43:45 -0400 | Subject | Re: [2.6.37-rc1] /proc/vmstat failure. |
| |
On Wed, Nov 3, 2010 at 7:11 AM, Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp> wrote: > > git bisect reported that commit 79da826aee6a10902ef411bc65864bd02102fa83 > "writeback: report dirty thresholds in /proc/vmstat" is first bad commit.
Have you verified that reverting that on top of current -git also fixes the problem (outside of just the bisected kernels)?
> Steps to reproduce: > Boot and login via SSH and do "cat /proc/vmstat". > > What is strange, this failure occurs when tty is /dev/pts/0 (i.e. > devpts filesystem / interactive ssh login session) and does not occur > when tty is /dev/tty1 (i.e. console login session).
It really sounds like memory corruption, likely because something has stepped on somebody elses allocation. One thing that patch does is to change the size of the allocation - perhaps it now ends up being in the same bucket size with some tty data structure?
Have you tried enabling SLUB/SLAB debugging?
Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |