Commit b4678df1 authored by Matthew Wilcox's avatar Matthew Wilcox Committed by Jeff Layton

errseq: Always report a writeback error once

The errseq_t infrastructure assumes that errors which occurred before
the file descriptor was opened are of no interest to the application.
This turns out to be a regression for some applications, notably Postgres.

Before errseq_t, a writeback error would be reported exactly once (as
long as the inode remained in memory), so Postgres could open a file,
call fsync() and find out whether there had been a writeback error on
that file from another process.

This patch changes the errseq infrastructure to report errors to all
file descriptors which are opened after the error occurred, but before
it was reported to any file descriptor.  This restores the user-visible

Fixes: 5660e13d ("fs: new infrastructure for writeback error handling and reporting")
Signed-off-by: default avatarMatthew Wilcox <>
Reviewed-by: default avatarJeff Layton <>
Signed-off-by: default avatarJeff Layton <>
parent 0644f186
......@@ -111,27 +111,22 @@ EXPORT_SYMBOL(errseq_set);
* errseq_sample() - Grab current errseq_t value.
* @eseq: Pointer to errseq_t to be sampled.
* This function allows callers to sample an errseq_t value, marking it as
* "seen" if required.
* This function allows callers to initialise their errseq_t variable.
* If the error has been "seen", new callers will not see an old error.
* If there is an unseen error in @eseq, the caller of this function will
* see it the next time it checks for an error.
* Context: Any context.
* Return: The current errseq value.
errseq_t errseq_sample(errseq_t *eseq)
errseq_t old = READ_ONCE(*eseq);
errseq_t new = old;
* For the common case of no errors ever having been set, we can skip
* marking the SEEN bit. Once an error has been set, the value will
* never go back to zero.
if (old != 0) {
if (old != new)
cmpxchg(eseq, old, new);
return new;
/* If nobody has seen this error yet, then we can be the first. */
if (!(old & ERRSEQ_SEEN))
old = 0;
return old;
Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment