| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | ASSERT in xlog_find_verify_log_record during xfs/098 |
| From: | Eric Sandeen <sandeen@xxxxxxxxxx> |
| Date: | Tue, 1 Mar 2016 13:04:58 -0600 |
| Cc: | Al Viro <viro@xxxxxxxxxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 |
Al mentioned that he hit an ASSERT during xfs/098, a log fuzzer
test, in xlog_find_verify_log_record():
for (i = (*last_blk) - 1; i >= 0; i--) {
if (i < start_blk) {
/* valid log record not found */
xfs_warn(log->l_mp,
"Log inconsistent (didn't find previous header)");
ASSERT(0);
error = -EIO;
goto out;
}
Should that assert even be there? Looks like it's gracefully
handled, I don't see offhand that anything should have caught
this corruption earlier, and we don't really want to bug on disk
corruption. Am I missing something?
Thanks,
-Eric
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] xfs: remove impossible condition, Christoph Hellwig |
|---|---|
| Next by Date: | [RFC PATCH] semaphore: fix uninitialized list_head vs list_force_poison, Dan Williams |
| Previous by Thread: | Re: block allocations for the refcount btree, Darrick J. Wong |
| Next by Thread: | Re: ASSERT in xlog_find_verify_log_record during xfs/098, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |