Hello Petr, Thanks for your reply. On 2014/9/17 14:47, Petr Tesarik wrote: >> Since the incomplete vmcore generated by ENOSPC error can't be anylyzed by >> >crash utility, but sometimes this file may contain important information > Hello ??, > > first of all, I like your patch. It has always annoyed me that any > incomplete dump was utterly useless. Just one small question: why is > this limited to ENOSPC? Why not e.g. EIO? EFBIG? At present, I just consider ENOSPC for this error maybe more common. And I'm considering to deal with other situations in the coming future. > I think writing the (incomplete) bitmap should always be attempted. > > Petr Tesarik > PS: Your Chinese must be very good, and my Chinese name is ?? :P -- Regards Wang Xiao
