cerc-io/lotus
16
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 27 Wiki Activity

Merge pull request #10259 from filecoin-project/steb/call-check-message-validity

Browse Source 
fix: stmgr: check message validity before invoking vm
This commit is contained in:
Aayush Rajasekaran 2023-02-13 21:29:19 -05:00 committed by GitHub
commit 3c4a83916b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
chain/stmgr/call.go
View File

@ -107,6 +107,14 @@ func (sm *StateManager) callInternal(ctx context.Context, msg *types.Message, pr
}
}
// This isn't strictly necessary, but the underlying VM will assume that the message is
// valid and may not return helpful debugging information. Checking here makes message
// validity issues easier to debug.
nv := sm.GetNetworkVersion(ctx, ts.Height())
if err := msg.ValidForBlockInclusion(0, nv); err != nil {
return nil, xerrors.Errorf("message not valid for network version %d: %w", nv, err)
}
// Unless executing on a specific state cid, apply all the messages from the current tipset
// first. Unfortunately, we can't just execute the tipset, because that will run cron. We
// don't want to apply miner messages after cron runs in a given epoch.