On Wed, Nov 15, 2017 at 02:16:01PM +0100, Holger Hoffstätte wrote:
> On 11/14/17 22:46, Darrick J. Wong wrote:
> (snip)
> > +static void iomap_warn_stale_pagecache(struct inode *inode)
> > +{
> > + errseq_set(&inode->i_mapping->wb_err, -EIO);
> > + pr_crit_ratelimited("Stale pagecache contents after collision "
> > + "between direct and buffered write!\n");
> > +}
>
> In this form the error message is IMHO useless since it tells me
> neither the file in question nor the misbehaving application.
> "Something went wrong somewhere" is not actionable information
> and in practice will only be ignored.
>
> Since you already have the inode in question at hand, print at least
> the full path + filename so that it's clear where things are going
> wrong. Usually that will let people deduce which application is
> misbehaving.
The whole point of the errseq_set call in this patch is to record the
write collision so that all the writers of this file will receive an EIO
the next time they try to flush the file. You can pinpoint exactly
which fd(s) in which application(s) caused the problem. The old dmesg
spew only captured which program issued the dio write.
(And the whole point of this patch is to see what people think about
that change of behavior w.r.t. us no longer letting userspace silently
corrupt the file...)
--D
> -h
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
