>> I disagree: you fix debian code but upstream kernel is also affected. >> I wanted to compile the upstream 4.4.26 for the COW fixe and cannot. >> Please revert.
$ rmadison linux linux | 4.5.5-1 | unstable | source linux | 4.5.5-1 | unstable-debug | source linux | 4.6.4-1 | unstable | source linux | 4.6.4-1 | unstable-debug | source linux | 4.7.5-1~bpo8+2 | jessie-backports | source linux | 4.7.5-1 | unstable | source linux | 4.7.6-1 | testing | source linux | 4.7.8-1~bpo8+1 | buildd-jessie-backports | source linux | 4.7.8-1~bpo8+1 | jessie-backports | source linux | 4.7.8-1 | buildd-unstable | source linux | 4.7.8-1 | unstable | source linux | 4.7.8-1 | unstable-debug | source You should be noted that building kernel from vanilla source isn't good idea in Debian. I don't see any 4.4 branch in Debian sources, but you may use git tag "debian/4.4.6-1" as base for your own work/fork. Happy hacking! PS: I can't understand why you're mixing GCC 6.x release (_unstable_) and Linux kernel 4.4.x long-term support (_stable_). If you're targeting on stable workflow, use GCC 5.x or even 4.9.x instead of 6.x branch. -- SY, Konstantin Demin
