From: Vegard Nossum <vegard.nossum@...> commit 12311959ecf8a3a64676c01b62ce67a0c5f0fd49 upstream. I got this: ================================================================================ UBSAN: Un

From: Vegard Nossum <vegard.nossum@...> commit 979515c5645830465739254abc1b1648ada41518 upstream. I ran into this: ================================================================================ UBSA

From: Seung-Woo Kim <sw0312.kim@...> commit 04d68dea26b0a409d44e87ea573a131b6dc67e78 upstream. From pwm_samsung_calc_tin(), there is routine to find the lowest divider possible to generate lower frequ

From: Xie XiuQi <xiexiuqi@...> commit ae0119f5f73b1e9cf7177fbbeea68d74c5751def upstream. Use 1UL for unsigned long, or we'll meet a overflow issue with UBSAN. [ 15.589489] UBSAN: Undefined behaviour i

From: Xie XiuQi <xiexiuqi@...> commit 79c350e45ebc5a718cc2d7114b45ad560069423d upstream. Use 1U for unsigned int to avoid a overflow warning from UBSAN. [ 31.910858] UBSAN: Undefined behaviour in fs/x

From: Eric Dumazet <edumazet@...> commit adb03115f4590baa280ddc440a8eff08a6be0cb7 upstream. Jiri Pirko reported an UBSAN warning happening in ip_idents_reserve() [] UBSAN: Undefined behaviour in ./arc

From: David Decotigny <decot@...> commit 5038056e6bd45788235e97e3bcfc43f96c52ca84 upstream. This also can address following UBSAN warnings: [ 36.640343] ===============================================

Hi, this is an overview of what is happening at CIP. Feel free to answer this mail with your bits. ++ Meetings * Members meeting on Mon Nov 28th ** The next f2f meeting will take place at ELC in Portl

CIP developer update, we're including outstanding problems as gitlab issues and there's more information at the issue links. CIP - On retrieving build artifacts - we still have issues here. Is it the

As before we're including outstanding problems as gitlab issues - read them for more information! CIP - build artifacts - we're still unable to retrieve these. We have manually installed later version

Hi, in the previous CIP Members meeting a question was made related with the 4.4 LTS kernel EOL (end of life). I have added to the wiki basic links that answers this question. Link: https://wiki.linux

* Virtual machine creation for the testing We've created 2 vagrant instances one for kernelci and the other for lava (lava is Debian based and kernelci is ubuntu based) work is in progress on merging

This is a backport of changes in 4.5 to extend the range of Address Space Layout Randomisation for user-space processes. When enabled, this should make some user-space vulnerabilities harder to exploi

Hi, running 'vagrant up' from a clean setup consistently fails with this: ==> default: TASK [setup] ******************************************************************* ==> default: ok: [kernel-ci-back

Hi, this is the report from the activities that Codethink is driving on and or involved. This week is not that we worked more but that we completed more tasks. ++ Meetings * Members meeting on Monday

In order to develop or debug the setup we should allow to a developer to use local copy of the sources. This is done by cloning all the remote repos to the project main folder. This folder is shared w

Hi Daniel, I like the change to the patch and I'll incorporate it tonight. We are already mirroring the KernelCI Backend and Frontend and I had almost the exact same thought this weekend that we alrea

Civil Infrastructure Platform (CIP) Continuous Integration of the CIP kernel using KernelCI and Testing the CIP kernel using LAVA Server v2 Hi Everyone, I am writing to give you an update on where we

Hi, during the past CIP Members meeting call, Monday 23rd January, Members agreed on bringing to the attention of CIP contributors and friends the Y2038 topic. What is Y2038 refers to? "Y2038 refers t

I've just released Linux version 4.4.48-cip2. There are no new CIP-specific changes; this just adds the fixes from stable versions 4.4.43-4.4.48 inclusive. I reviewed those fixes, but have only done v