Oh, having a filesystem sync entry point is much more than
a little cleanup. It's quite important. In current kernels
the same code path is used for both sync() and for periodic
kupdate writeback. It's not possible for the filesystem
to know which context it's being called in, and we do want
We want the sys_sync() path to wait on writeout, but it's
silly to make the kupdate path do that.
> > It then again starts I/O against new dirty data then waits on it again. And
> > then again. There's quite a lot of overkill there. But that's OK, as long
> > as it terminates sometime.
> /me doesn't comment
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/