| 1 |
On Sat, Dec 30, 2017 at 3:49 AM, Toralf Förster <toralf@g.o> wrote: |
| 2 |
> On 12/30/2017 07:52 AM, Alice Ferrazzi wrote: |
| 3 |
>> Hello, |
| 4 |
>> |
| 5 |
>> We recently dropped the stable keywords for 4.14, |
| 6 |
>> but 4.12 (the next stable in gentoo-sources) is no more |
| 7 |
>> maintained from upstream. |
| 8 |
>> |
| 9 |
>> The last update that 4.12 got from upstream was 2017-09-20, |
| 10 |
>> and upstream is no more backporting security fixes since then. |
| 11 |
>> Because of this, we will proceed to mask 4.12. |
| 12 |
>> |
| 13 |
>> Keep in mind: If 4.14 works for you, you can keyword it and |
| 14 |
>> continue to use it, if you need a more stable kernel, please |
| 15 |
>> move to 4.9. |
| 16 |
>> |
| 17 |
> At the LKML you can read that Linus Torvalds blames Gentoo GCC patch |
| 18 |
> set for few issues related to 4.14.9 |
| 19 |
> |
| 20 |
|
| 21 |
Not the patch set so much as gcc itself and the hardened profile |
| 22 |
enabling of -fstack-protector in the spec. It sounds like upstream |
| 23 |
may explicitly disable it, but it probably wouldn't hurt for the |
| 24 |
ebuilds to do so as well if it is known to cause problems, at least |
| 25 |
until gcc fixes whatever they're doing wrong. |
| 26 |
|
| 27 |
https://lkml.org/lkml/2017/12/29/488 |
| 28 |
|
| 29 |
-- |
| 30 |
Rich |
Archives