2018-10-16 09:43:49 -07:00
|
|
|
[package]
|
2019-06-12 08:49:59 -07:00
|
|
|
name = "solana-bpf-loader-program"
|
2023-06-02 08:08:07 -07:00
|
|
|
description = "Solana BPF loader"
|
2021-03-10 12:46:17 -08:00
|
|
|
documentation = "https://docs.rs/solana-bpf-loader-program"
|
2023-02-23 06:01:54 -08:00
|
|
|
version = { workspace = true }
|
|
|
|
|
authors = { workspace = true }
|
|
|
|
|
repository = { workspace = true }
|
|
|
|
|
homepage = { workspace = true }
|
|
|
|
|
license = { workspace = true }
|
|
|
|
|
edition = { workspace = true }
|
2018-10-16 09:43:49 -07:00
|
|
|
|
|
|
|
|
[dependencies]
|
2023-02-23 06:01:54 -08:00
|
|
|
bincode = { workspace = true }
|
|
|
|
|
byteorder = { workspace = true }
|
|
|
|
|
libsecp256k1 = { workspace = true }
|
|
|
|
|
log = { workspace = true }
|
|
|
|
|
rand = { workspace = true }
|
direct mapping: misc fixes (#32649)
* transaction_context: update make_data_mut comment
* bpf_loader: cpi: pass SerializeAccountMetadata to CallerAccount::from*
We now have a way to provide CallerAccount with trusted values coming
from our internal serialization code and not from untrusted vm space
* bpf_loader: direct_mapping: enforce account info pointers to be immutable
When direct mapping is enabled, we might need to update account data
memory regions across CPI calls. Since the only way we have to retrieve
the regions is based on their vm addresses, we enforce vm addresses to
be stable. Accounts can still be mutated and resized of course, but it
must be done in place.
This also locks all other AccountInfo pointers, since there's no legitimate
reason to make them point to anything else.
* bpf_loader: cpi: access ref_to_len_in_vm through VmValue
Direct mapping needs to translate vm values at each access since
permissions of the underlying memory might have changed.
* direct mapping: improve memory permission tracking across CPI calls
Ensure that the data and realloc regions of an account always track the
account's permissions. In order to do this, we also need to split
realloc regions in their own self contained regions, where before we
had:
[account fields][account data][account realloc + more account fields + next account fields][next account data][...]
we now have:
[account fields][account data][account realloc][more account fields + next account fields][next account data][...]
Tested in TEST_[FORBID|ALLOW]_WRITE_AFTER_OWNERSHIP_CHANGE*
Additionally when direct mapping is on, we must update all perms at once before
doing account data updates. Otherwise, updating an account might write into
another account whose perms we haven't updated yet. Tested in
TEST_FORBID_LEN_UPDATE_AFTER_OWNERSHIP_CHANGE.
* bpf_loader: serialization: address review comment don't return vm_addr from push_account_region
* bpf_loader: rename push_account_region to push_account_data_region
* cpi: fix slow edge case zeroing extra account capacity after shrinking an account
When returning from CPI we need to zero all the account memory up to the
original length only if we know we're potentially dealing with uninitialized
memory.
When we know that the spare capacity has deterministic content, we only need to
zero new_len..prev_len.
This fixes a slow edge case that was triggerable by the following scenario:
- load a large account (say 10MB) into the vm
- shrink to 10 bytes - would memset 10..10MB
- shrink to 9 bytes - would memset 9..10MB
- shrink to 8 bytes - would memset 8..10MB
- ...
Now instead in the scenario above the following will happen:
- load a large account (say 10MB) into the vm
- shrink to 10 bytes - memsets 10..10MB
- shrink to 9 bytes - memsets 9..10
- shrink to 8 bytes - memset 8..9
- ...
* bpf_loader: add account_data_region_memory_state helper
Shared between serialization and CPI to figure out the MemoryState of an
account.
* cpi: direct_mapping: error out if ref_to_len_in_vm points to account memory
If ref_to_len_in_vm is allowed to be in account memory, calles could mutate it,
essentially letting callees directly mutate callers memory.
* bpf_loader: direct_mapping: map AccessViolation -> InstructionError
Return the proper ReadonlyDataModified / ExecutableDataModified /
ExternalAccountDataModified depending on where the violation occurs
* bpf_loader: cpi: remove unnecessary infallible slice::get call
2023-08-30 02:57:24 -07:00
|
|
|
scopeguard = { workspace = true }
|
2023-02-23 06:01:54 -08:00
|
|
|
solana-measure = { workspace = true }
|
|
|
|
|
solana-program-runtime = { workspace = true }
|
|
|
|
|
solana-sdk = { workspace = true }
|
|
|
|
|
solana-zk-token-sdk = { workspace = true }
|
|
|
|
|
solana_rbpf = { workspace = true }
|
|
|
|
|
thiserror = { workspace = true }
|
2018-10-16 09:43:49 -07:00
|
|
|
|
2023-02-16 05:16:25 -08:00
|
|
|
[dev-dependencies]
|
2023-08-30 10:48:27 -07:00
|
|
|
assert_matches = { workspace = true }
|
2023-05-19 13:47:14 -07:00
|
|
|
memoffset = { workspace = true }
|
2023-07-13 06:44:08 -07:00
|
|
|
solana-sdk = { workspace = true, features = ["dev-context-only-utils"] }
|
2023-02-16 05:16:25 -08:00
|
|
|
|
2018-10-16 09:43:49 -07:00
|
|
|
[lib]
|
2020-08-14 12:32:45 -07:00
|
|
|
crate-type = ["lib"]
|
2019-06-12 08:49:59 -07:00
|
|
|
name = "solana_bpf_loader_program"
|
2020-04-16 18:18:28 -07:00
|
|
|
|
|
|
|
|
[package.metadata.docs.rs]
|
|
|
|
|
targets = ["x86_64-unknown-linux-gnu"]
|
