On Wed, 2010-12-22 at 08:32 +0800, David Howells wrote: > Huang Ying <ying.huang@xxxxxxxxx> wrote: > > > The user space program (syslogd) is in my big picture, it will guarantee > > an oops meesage actually go to disk via something like fsync. After > > doing that, the user space program can erase the corresponding record in > > persistent storage to free the space. So all in all, oops messages not > > causing system panic or disk error will go to disk eventually and being > > freed and will not use up the persistent storage. > > I see. So you rely on fsync() to hang forever if the message can't be written > to disk because an oops killed the write path? Yes. Or fsync() report error. Best Regards, Huang Ying -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
