kernel patching - how to check / verify when specific patch was applied
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
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?
apt kernel dpkg patch
add a comment |Â
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?
apt kernel dpkg patch
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
add a comment |Â
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?
apt kernel dpkg patch
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
apt kernel dpkg patch
edited Mar 13 at 12:49
![](https://i.stack.imgur.com/ofQEO.jpg?s=32&g=1)
![](https://i.stack.imgur.com/ofQEO.jpg?s=32&g=1)
Maki
1376
1376
asked Mar 13 at 12:27
![](https://i.stack.imgur.com/ohHGF.jpg?s=32&g=1)
![](https://i.stack.imgur.com/ohHGF.jpg?s=32&g=1)
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
add a comment |Â
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
add a comment |Â
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.
That seems like very good solution, thank you @doug-smythies
â bogdan
Mar 13 at 15:04
add a comment |Â
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.
That seems like very good solution, thank you @doug-smythies
â bogdan
Mar 13 at 15:04
add a comment |Â
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.
That seems like very good solution, thank you @doug-smythies
â bogdan
Mar 13 at 15:04
add a comment |Â
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.
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.
answered Mar 13 at 15:02
![](https://i.stack.imgur.com/quzhv.png?s=32&g=1)
![](https://i.stack.imgur.com/quzhv.png?s=32&g=1)
Doug Smythies
6,33631426
6,33631426
That seems like very good solution, thank you @doug-smythies
â bogdan
Mar 13 at 15:04
add a comment |Â
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
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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