forks/linsk
forks/linsk
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix versioning

Browse source
This commit is contained in:
AlexSSD7 2023-09-28 11:03:40 +01:00
commit 3dfce906d9
3 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -44,7 +44,7 @@ Linsk relies on network file shares to expose files to the host machine. Below a
# ⚠️ Serious bug disclosures (Obsolete versions) # ⚠️ Serious bug disclosures (Obsolete versions)
Linsk versions below **v1.1.0** are considered obsolete **UNLESS**: Linsk versions below **v0.2.0** are considered obsolete **UNLESS**:
* The use of Linsk was limited exclusively to devices with a 512-byte logical block (sector) size. * The use of Linsk was limited exclusively to devices with a 512-byte logical block (sector) size.
* The experimental USB passthrough was used. * The experimental USB passthrough was used.

4
serious-bug-disclosures/README.md
View file

@ -2,10 +2,10 @@
## Obsolete versions (Summary) ## Obsolete versions (Summary)
Linsk versions below **v1.1.0** are considered obsolete **UNLESS**: Linsk versions below **v0.2.0** are considered obsolete **UNLESS**:
* The use of Linsk was limited exclusively to devices with a 512-byte logical block (sector) size. * The use of Linsk was limited exclusively to devices with a 512-byte logical block (sector) size.
* The experimental USB passthrough was used. * The experimental USB passthrough was used.
## Index ## Index
* [Faulty raw device block size detection](faulty-block-size-detection.md) (Fixed in: **v1.1.0**, Affected: **<v1.1.0**, Severity: **High**) * [Faulty raw device block size detection](faulty-block-size-detection.md) (Fixed in: **v0.2.0**, Affected: **<v0.2.0**, Severity: **High**)

6
serious-bug-disclosures/faulty-block-size-detection.md
View file

@ -2,7 +2,7 @@
## Key Aspects ## Key Aspects
* **Affected versions**: below v1.1.0. * **Affected versions**: below v0.2.0.
* **Affected *UNLESS***: * **Affected *UNLESS***:
* The use of Linsk was limited exclusively to devices with a 512-byte logical block (sector) size. * The use of Linsk was limited exclusively to devices with a 512-byte logical block (sector) size.
* The experimental USB passthrough was used. * The experimental USB passthrough was used.
@ -11,7 +11,7 @@
## Brief description ## Brief description
Prior to version v1.1.0, Linsk assumed that the block size detection was done by QEMU. However, that wasn't the case. QEMU used a default block size of 512 bytes, no matter the physical/logical block (sector) size of the actual drive. Prior to version v0.2.0, Linsk assumed that the block size detection was done by QEMU. However, that wasn't the case. QEMU used a default block size of 512 bytes, no matter the physical/logical block (sector) size of the actual drive.
Originally, this was not an issue as the emulated block size of 512 bytes did not hinder mounting, reading, and writing the files to the disk. However, if a significant amount of writes were committed to the drive, the OS may attempt to optimize the file system(s). This is a problem since all possible optimizations will assume the emulated 512-byte block size to be the real logical block size. If this happens, the drive will get effectively locked to the emulated block size of 512 bytes. In that case, the host OS that recognizes a valid block size of over 512 bytes will not be able to access the files and/or recognize any of the filesystems in the disk. Originally, this was not an issue as the emulated block size of 512 bytes did not hinder mounting, reading, and writing the files to the disk. However, if a significant amount of writes were committed to the drive, the OS may attempt to optimize the file system(s). This is a problem since all possible optimizations will assume the emulated 512-byte block size to be the real logical block size. If this happens, the drive will get effectively locked to the emulated block size of 512 bytes. In that case, the host OS that recognizes a valid block size of over 512 bytes will not be able to access the files and/or recognize any of the filesystems in the disk.
@ -19,7 +19,7 @@ The solution to recover from this condition is to copy the files to another (tem
## Compatibility ## Compatibility
Linsk v1.1.0 is packaged with a custom `dev_faulty_bs` device type that preserves the original behavior that implied the use of the faulty block size detection. This should not be used for anything else but to recover the files from a drive that was locked to the emulated 512-byte block size. Linsk v0.2.0 is packaged with a custom `dev_faulty_bs` device type that preserves the original behavior that implied the use of the faulty block size detection. This should not be used for anything else but to recover the files from a drive that was locked to the emulated 512-byte block size.
Example use: Example use:
```sh ```sh