Gustavo Moreira

> maybe better going backwards 64, 32, 16, 8, 1 ... and keeping the already tested address in a set hm actually, if we are going to test each byte,...

@Abyss-W4tcher only 1 byte and 8 bytes alignments. It was just to see how this would impact performance. ```python module_address_alignment = 1 # 8 # cls._get_module_address_alignment(context, vmlinux_module_name) ```

Okay, I made the fast scan method the default. Removed the vol2 implementation and updated the plugin to fall back to 1-byte alignment scanning if addresses aren't aligned with the...

Cool, it's ready to go. Thanks @ikelos

fix: #1438

If, in a hypothetical scenario, a pointer to 0 is readable in a specific layer and someone wants to check for 0 specifically, why are they evaluating it as a...

Hey @ikelos, the tests are failing because the ISF in linux.zip (`linux-image-3.2.0-4-amd64-dbg_3.2.57-3+deb7u2_amd64.json.xz`) doesn't contain the symbol types. So in [this](https://github.com/volatilityfoundation/volatility3/pull/1317/files#diff-dc8047d2b21ebae7092368b7efe49ec11221e192735929c2be49998e31335956R512) line the call to `vmlinux.object_from_symbol()` returns a void type which...

@ikelos Alright, merge conflict resolved. It will be good to go once the ISF is fixed.

@ikelos the ISF is now fixed, I reran the tests and it passed. it's ready to go!!

This is precisely the case with the current ISF for the `linux-sample-1.bin` sample in the github actions. See [this](https://github.com/volatilityfoundation/volatility3/pull/1283/files#diff-e5a8a9af6057f1e6e2579f04f7ec5567f6fc9f7e32f74175332b280237964336R66). It might be worth considering accepting a tuple as well.. see...