Hugh Dickins wrote:
> > "[2.6.36-rc1] Bugs in __free_pipe_info()".
>
> That's good, but puzzling. I'll mention it in the patch comment, since
> that's what you've found: but I've given up trying to understand how.
Yeah, it's puzzling. What I was doing is
./newns ./foo | grep -vF OK
where "./newns" calls mount("tmpfs") after clone(CLONE_NEWNS)
and ./foo calls chroot()/mount("tmpfs")/umount()/pivot_root() etc.
After applying your patch, I can no longer reproduce __free_pipe_info() errors.
I don't know why __free_pipe_info() errors are reported on "grep" rather than
"newns" or "foo". But if the cause of __free_pipe_info() errors was memory
corruption by the bug in shmem, it is possible that fixing the bug in shmem
solves __free_pipe_info() errors.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
