kernel patching - how to check / verify when specific patch was applied

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
2
down vote

favorite












How do I find/verify, IF and WHEN a specific patch for example this one, have been added to the kernel?



One way I can think off (not very efficient) would be to download all kernels since the patch was logged, and look into change log file. Example:



$ apt-get changelog linux-image-4.4.0-116-generic


How do you approach this type of problems?










share|improve this question



















  • 1




    See unix.stackexchange.com/questions/45120/… . There are several suggestions
    – Panther
    Mar 13 at 14:58











  • Very useful, Thanks @Panther
    – bogdan
    Mar 13 at 15:05














up vote
2
down vote

favorite












How do I find/verify, IF and WHEN a specific patch for example this one, have been added to the kernel?



One way I can think off (not very efficient) would be to download all kernels since the patch was logged, and look into change log file. Example:



$ apt-get changelog linux-image-4.4.0-116-generic


How do you approach this type of problems?










share|improve this question



















  • 1




    See unix.stackexchange.com/questions/45120/… . There are several suggestions
    – Panther
    Mar 13 at 14:58











  • Very useful, Thanks @Panther
    – bogdan
    Mar 13 at 15:05












up vote
2
down vote

favorite









up vote
2
down vote

favorite











How do I find/verify, IF and WHEN a specific patch for example this one, have been added to the kernel?



One way I can think off (not very efficient) would be to download all kernels since the patch was logged, and look into change log file. Example:



$ apt-get changelog linux-image-4.4.0-116-generic


How do you approach this type of problems?










share|improve this question















How do I find/verify, IF and WHEN a specific patch for example this one, have been added to the kernel?



One way I can think off (not very efficient) would be to download all kernels since the patch was logged, and look into change log file. Example:



$ apt-get changelog linux-image-4.4.0-116-generic


How do you approach this type of problems?







apt kernel dpkg patch






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 13 at 12:49









Maki

1376




1376










asked Mar 13 at 12:27









bogdan

123112




123112







  • 1




    See unix.stackexchange.com/questions/45120/… . There are several suggestions
    – Panther
    Mar 13 at 14:58











  • Very useful, Thanks @Panther
    – bogdan
    Mar 13 at 15:05












  • 1




    See unix.stackexchange.com/questions/45120/… . There are several suggestions
    – Panther
    Mar 13 at 14:58











  • Very useful, Thanks @Panther
    – bogdan
    Mar 13 at 15:05







1




1




See unix.stackexchange.com/questions/45120/… . There are several suggestions
– Panther
Mar 13 at 14:58





See unix.stackexchange.com/questions/45120/… . There are several suggestions
– Panther
Mar 13 at 14:58













Very useful, Thanks @Panther
– bogdan
Mar 13 at 15:05




Very useful, Thanks @Panther
– bogdan
Mar 13 at 15:05










1 Answer
1






active

oldest

votes

















up vote
2
down vote



accepted










One way is to use the a git clone of the source and search for the patch.
Mine is a clone of the mainline source from kernel.org:



git log --oneline | grep "add DISCARD support to virtio-blk driver"


did not find anything. As a sanity check, look at the code itself and manually observe if the patch was ever applied or not. I looked at drivers/block/virtio_blk.c and didn't see the patch.



Conclusion: the patch was never applied to the mainline kernel, and therefore I very much doubt that it would ever have been backported to previous kernels.






share|improve this answer




















  • That seems like very good solution, thank you @doug-smythies
    – bogdan
    Mar 13 at 15:04











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1014539%2fkernel-patching-how-to-check-verify-when-specific-patch-was-applied%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
2
down vote



accepted










One way is to use the a git clone of the source and search for the patch.
Mine is a clone of the mainline source from kernel.org:



git log --oneline | grep "add DISCARD support to virtio-blk driver"


did not find anything. As a sanity check, look at the code itself and manually observe if the patch was ever applied or not. I looked at drivers/block/virtio_blk.c and didn't see the patch.



Conclusion: the patch was never applied to the mainline kernel, and therefore I very much doubt that it would ever have been backported to previous kernels.






share|improve this answer




















  • That seems like very good solution, thank you @doug-smythies
    – bogdan
    Mar 13 at 15:04















up vote
2
down vote



accepted










One way is to use the a git clone of the source and search for the patch.
Mine is a clone of the mainline source from kernel.org:



git log --oneline | grep "add DISCARD support to virtio-blk driver"


did not find anything. As a sanity check, look at the code itself and manually observe if the patch was ever applied or not. I looked at drivers/block/virtio_blk.c and didn't see the patch.



Conclusion: the patch was never applied to the mainline kernel, and therefore I very much doubt that it would ever have been backported to previous kernels.






share|improve this answer




















  • That seems like very good solution, thank you @doug-smythies
    – bogdan
    Mar 13 at 15:04













up vote
2
down vote



accepted







up vote
2
down vote



accepted






One way is to use the a git clone of the source and search for the patch.
Mine is a clone of the mainline source from kernel.org:



git log --oneline | grep "add DISCARD support to virtio-blk driver"


did not find anything. As a sanity check, look at the code itself and manually observe if the patch was ever applied or not. I looked at drivers/block/virtio_blk.c and didn't see the patch.



Conclusion: the patch was never applied to the mainline kernel, and therefore I very much doubt that it would ever have been backported to previous kernels.






share|improve this answer












One way is to use the a git clone of the source and search for the patch.
Mine is a clone of the mainline source from kernel.org:



git log --oneline | grep "add DISCARD support to virtio-blk driver"


did not find anything. As a sanity check, look at the code itself and manually observe if the patch was ever applied or not. I looked at drivers/block/virtio_blk.c and didn't see the patch.



Conclusion: the patch was never applied to the mainline kernel, and therefore I very much doubt that it would ever have been backported to previous kernels.







share|improve this answer












share|improve this answer



share|improve this answer










answered Mar 13 at 15:02









Doug Smythies

6,33631426




6,33631426











  • That seems like very good solution, thank you @doug-smythies
    – bogdan
    Mar 13 at 15:04

















  • That seems like very good solution, thank you @doug-smythies
    – bogdan
    Mar 13 at 15:04
















That seems like very good solution, thank you @doug-smythies
– bogdan
Mar 13 at 15:04





That seems like very good solution, thank you @doug-smythies
– bogdan
Mar 13 at 15:04


















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1014539%2fkernel-patching-how-to-check-verify-when-specific-patch-was-applied%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491