Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mlyle
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
2025 ms
·
6091.
▲
by
mlyle
9y ago
Well, the very idea that there is some timelimit on mitigation before the flaw is disclosed anyways is that "very weak tea". However, overall, I agree with you. Person with exploit needs to compare the probable consequences of
6092.
▲
by
mlyle
9y ago
Read. :P To quote what you replied to: "And there's many other callers of this function that are potentially getting bad results, along with other cousins like bio_clone_bioset that are still unfixed. " bcache doesn't
6093.
▲
by
mlyle
9y ago
TravisCI generally tests the end result of a PR, not all intermediate states. I have a continuous integration tool for bcache in place, but it's more geared on end states-- compiling/checkpatch/test sequence.
6094.
▲
by
mlyle
9y ago
As pointed out elsewhere, I never accepted this patchset. But: For stuff I accept, I try and make sure that intermediate states compile, but I can't promise I run a compile on every intermediate step or that my review eye is good enoug
6095.
▲
by
mlyle
9y ago
No-- the cloning operation didn't preserve the partition information. When I first bisected/found the issue I thought it was as you describe, but it's really just that cloning 0'd it out in the new copy and everything e
6096.
▲
by
mlyle
9y ago
The important distinction is where the critical information on where the device offset is encoded from. Before it was specified by whether a partition or parent disk device was used; now it is always the actual disk and a partition number.