kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
* Best practice to upgrade kernel
@ 2019-04-26 18:17 Xiaolong Wang
  2019-04-26 19:35 ` Valdis Klētnieks
  2019-04-26 20:11 ` Greg KH
  0 siblings, 2 replies; 3+ messages in thread
From: Xiaolong Wang @ 2019-04-26 18:17 UTC (permalink / raw)
  To: kernelnewbies

Hi all,

I have a newbie question. I’m using a 3.18.66 kernel branch from Qualcomm. Over the year I’ve applied some of patched here and there manually.

But It seems Qualcomm does not patch lot of newly released vulnerabilities. I would love to upgrade to the latest 3.18.138 (not 4.x)

What is the best practice here? 

Thanks
-Dan
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Best practice to upgrade kernel
  2019-04-26 18:17 Best practice to upgrade kernel Xiaolong Wang
@ 2019-04-26 19:35 ` Valdis Klētnieks
  2019-04-26 20:11 ` Greg KH
  1 sibling, 0 replies; 3+ messages in thread
From: Valdis Klētnieks @ 2019-04-26 19:35 UTC (permalink / raw)
  To: Xiaolong Wang; +Cc: kernelnewbies

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 681 bytes --]

On Fri, 26 Apr 2019 11:17:24 -0700, Xiaolong Wang said:

> I have a newbie question. I’m using a 3.18.66 kernel branch from Qualcomm.
> Over the year I’ve applied some of patched here and there manually.

> But It seems Qualcomm does not patch lot of newly released vulnerabilities. I
> would love to upgrade to the latest 3.18.138 (not 4.x)

> What is the best practice here? 

Since you're being forced by Qualcomm to use 3.18, take it up with them.

What's this? You say you're not forced to do it?  Well, there's two things you
can do:

1) Continue feeling the pain of running an old kernel
2) Fix the reason you're on 3.18, and get on a 4.x or 5.x kernel.

Your choice.



[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Best practice to upgrade kernel
  2019-04-26 18:17 Best practice to upgrade kernel Xiaolong Wang
  2019-04-26 19:35 ` Valdis Klētnieks
@ 2019-04-26 20:11 ` Greg KH
  1 sibling, 0 replies; 3+ messages in thread
From: Greg KH @ 2019-04-26 20:11 UTC (permalink / raw)
  To: Xiaolong Wang; +Cc: kernelnewbies

On Fri, Apr 26, 2019 at 11:17:24AM -0700, Xiaolong Wang wrote:
> Hi all,
> 
> I have a newbie question. I’m using a 3.18.66 kernel branch from Qualcomm. Over the year I’ve applied some of patched here and there manually.
> 
> But It seems Qualcomm does not patch lot of newly released vulnerabilities. I would love to upgrade to the latest 3.18.138 (not 4.x)
> 
> What is the best practice here? 

Merge your branch with the android-common 3.18 branch, and try to run
that.  Note, there will be some conflicts, and I think there's a random
qualcomm branch somewhere on code aurora somewhere that has those
problems resolved if you have problems with them.

good luck, it's possible to do (I have a phone running the latest 3.18
release on it with a qcom chipset), but it all depends on exactly what
device you have as to how easy/hard it is going to be!

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-04-26 20:11 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-04-26 18:17 Best practice to upgrade kernel Xiaolong Wang
2019-04-26 19:35 ` Valdis Klētnieks
2019-04-26 20:11 ` Greg KH

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).