Age | Commit message (Collapse) | Author |
|
Change-Id: Icae4dad43767669522d97cbf780c4de702266b95
|
|
cc737d2b64
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/gptfdisk/+/11603732
Change-Id: I9dc7129bb58a9f7789a0bb224daa4780a80d5e6d
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/gptfdisk/+/11603732
Change-Id: I833de27622d6b0e1a5d3a9bf30fae6771462eee3
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/external/gptfdisk/+/11603731
Change-Id: I243251b78b4a22544de86641a1bc2d8c09bb2ed9
|
|
|
|
|
|
Change-Id: Icbbae670dc6426029076e9c225f715eacffbe2c1
|
|
586c4df257 am: 99bbb78a37 am: 4841ffd80c am: bab8403b53
Original change: undetermined
Change-Id: I06cc9b52ea6ad14c1f00280a8ef60cf3a50c6638
|
|
586c4df257 am: 99bbb78a37 am: 4841ffd80c
Original change: undetermined
Change-Id: I105de040d119c061b42e7a23bffa230d28371443
|
|
586c4df257 am: 99bbb78a37
Original change: undetermined
Change-Id: I187989b4e2330a91c3fa63d3eaa1e62cd41c6b8c
|
|
586c4df257
Original change: undetermined
Change-Id: Idf6e97a5776f61f9e7fe585364862b1d66bc75e3
|
|
256b5261a4 am: 5d9a2fdafe
Original change: undetermined
Change-Id: I0c8b88aed9f28b6d153506312e4c7b954d63c3ab
|
|
dac372ca47
Original change: undetermined
Change-Id: Ie121dea00a83ccbc960840645574a2c61cbb46bb
|
|
256b5261a4
Original change: undetermined
Change-Id: I471e51aba1d9f14292db0648a918cc1d062853d0
|
|
Original change: undetermined
Change-Id: I658cbb56894414db79344d5a45ec26a3bcd04731
|
|
Original change: undetermined
Change-Id: Ie7e649e1bd734af511e1efbd0af265a61a1057ee
|
|
Original change: undetermined
Change-Id: I9052f2349633cd5ceb1d35768a9cb5b5523b32d1
|
|
Original change: undetermined
Change-Id: Ide8ae337c93d3fb20d7b6333b72cf4c9d86d6710
|
|
Original change: undetermined
Change-Id: I71cd4208bd4d233053255e0c893a1c31bcbc2153
|
|
Original change: undetermined
Change-Id: I0c7dc499ec9b1df80708f1ed153e90d33ae67080
|
|
If a maliciously formatted USB or SD Card device was inserted into an
Android device, the sgdisk tool could crash. This crash occurs because
sgdisk does not validate that the number of GPT partition entries
specified on disk matches the internal maximum permitted by the GPT spec.
Fix this by sanity checking the on disk parameter before using it.
After the fix, sgdisk detects the corrupt GPT during the formatting
procedure, but it is harmlessly zapped and replaced with a new one.
Test: before fix, saw sgdisk crash while the device was booting up
Test: after fix, no more sgdisk crashes
Test: went through "portable storage" and "adopted storage" wizard flows
using the cuttlefish virtual device and a malicious partition
table flashed to the device
Bug: 152874864
Change-Id: Iec64bc2ef5c31ad985126f9cf3b755eec7de3abe
|
|
If a maliciously formatted USB or SD Card device was inserted into an
Android device, the sgdisk tool could crash. This crash occurs because
sgdisk does not validate that the number of GPT partition entries
specified on disk matches the internal maximum permitted by the GPT spec.
Fix this by sanity checking the on disk parameter before using it.
After the fix, sgdisk detects the corrupt GPT during the formatting
procedure, but it is harmlessly zapped and replaced with a new one.
Test: before fix, saw sgdisk crash while the device was booting up
Test: after fix, no more sgdisk crashes
Test: went through "portable storage" and "adopted storage" wizard flows
using the cuttlefish virtual device and a malicious partition
table flashed to the device
Bug: 152874864
Change-Id: Iec64bc2ef5c31ad985126f9cf3b755eec7de3abe
|
|
If a maliciously formatted USB or SD Card device was inserted into an
Android device, the sgdisk tool could crash. This crash occurs because
sgdisk does not validate that the number of GPT partition entries
specified on disk matches the internal maximum permitted by the GPT spec.
Fix this by sanity checking the on disk parameter before using it.
After the fix, sgdisk detects the corrupt GPT during the formatting
procedure, but it is harmlessly zapped and replaced with a new one.
Test: before fix, saw sgdisk crash while the device was booting up
Test: after fix, no more sgdisk crashes
Test: went through "portable storage" and "adopted storage" wizard flows
using the cuttlefish virtual device and a malicious partition
table flashed to the device
Bug: 152874864
Change-Id: Iec64bc2ef5c31ad985126f9cf3b755eec7de3abe
|
|
If a maliciously formatted USB or SD Card device was inserted into an
Android device, the sgdisk tool could crash. This crash occurs because
sgdisk does not validate that the number of GPT partition entries
specified on disk matches the internal maximum permitted by the GPT spec.
Fix this by sanity checking the on disk parameter before using it.
After the fix, sgdisk detects the corrupt GPT during the formatting
procedure, but it is harmlessly zapped and replaced with a new one.
Test: before fix, saw sgdisk crash while the device was booting up
Test: after fix, no more sgdisk crashes
Test: went through "portable storage" and "adopted storage" wizard flows
using the cuttlefish virtual device and a malicious partition
table flashed to the device
Bug: 152874864
Change-Id: Iec64bc2ef5c31ad985126f9cf3b755eec7de3abe
|
|
If a maliciously formatted USB or SD Card device was inserted into an
Android device, the sgdisk tool could crash. This crash occurs because
sgdisk does not validate that the number of GPT partition entries
specified on disk matches the internal maximum permitted by the GPT spec.
Fix this by sanity checking the on disk parameter before using it.
After the fix, sgdisk detects the corrupt GPT during the formatting
procedure, but it is harmlessly zapped and replaced with a new one.
Test: before fix, saw sgdisk crash while the device was booting up
Test: after fix, no more sgdisk crashes
Test: went through "portable storage" and "adopted storage" wizard flows
using the cuttlefish virtual device and a malicious partition
table flashed to the device
Bug: 152874864
Change-Id: Iec64bc2ef5c31ad985126f9cf3b755eec7de3abe
|
|
Change-Id: I0c874fd90f6520b8eba64d98e48d1b04c6549893
|
|
If a maliciously formatted USB or SD Card device was inserted into an
Android device, the sgdisk tool could crash. This crash occurs because
sgdisk does not validate that the number of GPT partition entries
specified on disk matches the internal maximum permitted by the GPT spec.
Fix this by sanity checking the on disk parameter before using it.
After the fix, sgdisk detects the corrupt GPT during the formatting
procedure, but it is harmlessly zapped and replaced with a new one.
Test: before fix, saw sgdisk crash while the device was booting up
Test: after fix, no more sgdisk crashes
Test: went through "portable storage" and "adopted storage" wizard flows
using the cuttlefish virtual device and a malicious partition
table flashed to the device
Bug: 152874864
Change-Id: Iec64bc2ef5c31ad985126f9cf3b755eec7de3abe
|
|
Change-Id: I2facffa7c316def4c61a4d9d9ef34446f091cbd1
|
|
am: dc0e6b8dcf am: 0f57984be8
Change-Id: I31310e3dcac7bddb422bf6a2116d7da46e52e3c3
|
|
am: dc0e6b8dcf
Change-Id: I0fd23cdea1df8310c0fefaffc2025a392d442cac
|
|
Change-Id: I3cc47d2ae6c5f6afac8c7226bb3c99b7da0b9034
|
|
Change 2c2deeb032f6c158cf4f782e1765a4a21af88cb3 is reverted in this
merge. Because it conflicts with upstream option "move-main-table".
Change-Id: I2c1cb67a95139879333a430eb0e8b34f6b396c32
|
|
https://sourceforge.net/p/gptfdisk/code/merge-requests/17/
|
|
https://sourceforge.net/p/gptfdisk/code/merge-requests/16/
|
|
https://sourceforge.net/p/gptfdisk/code/merge-requests/14/
|
|
See https://github.com/systemd/systemd/pull/14390 .
|
|
|
|
Change-Id: I7b339ae380ef5cf089f30e57aea3b432a9c36cbc
|
|
Change-Id: I2eda3d550eb34134b7140489ab9b24759d279e34
|
|
Change-Id: I3fd2a2d76770c99af137c638c5d871240f48c609
|
|
am: 0da7f5dd73
Change-Id: I2a98d83c48192ba6f9fc4a23e18a4693b72311f5
|
|
Test: gerrit
Change-Id: I68bfa1493c42de5c27cca5ed8f9a6e28668346e3
|
|
uClibc++ does not implicitly do this.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
|
|
uClibc++ does not implicitly do this before getline.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
|
|
uClibc++ does not implicitly flush cout before getline.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
|
|
Needed with uClibc++ as it doesn't implicitly include it.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
|
|
Some hardware (notably Raspberry PI) requires a small FAT partition be listed
as the first MBR partition to boot. At the moment hybrid MBR disks allowing
this can only be made using the interactive `gdisk` program by choosing `h`
from the recovery menu and answering `N` when asked:
```
Place EFI GPT (0xEE) partition first in MBR (good for GRUB)?
```
This commit brings feature parity to `sgdisk` by changing `-h` to support an
optional final partition `EE` indicating that the GPT partition should be
listed last in the MBR instead of first.
**Examples**:
GPT first (current behaviour)
```shell
sgdisk -h 1:2 sdcard.img
```
GPT last
```shell
sgdisk -h 1:2:EE sdcard.img
```
|
|
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
[Retrieved from:
https://git.buildroot.net/buildroot/tree/package/gptfdisk/0001-ldlibs.patch]
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
|
|
Fix links to other manuals.
Change one MB to MiB.
Add space between number and unit.
|
|
|