| 1 |
___Google Summer of Code summary week 09___ |
| 2 |
|
| 3 |
|
| 4 |
What I did in this week 09 summary: |
| 5 |
|
| 6 |
elivepatch: |
| 7 |
|
| 8 |
* Fix return message for cve option |
| 9 |
* Added different configuration example [4.9.30,4.10.17] |
| 10 |
* Catch gentoo-sources not available error |
| 11 |
* Catch missing livepatch errors on the client |
| 12 |
- working on incremental patch features design and implementatio |
| 13 |
- putting patch files under /tmp/elivepatch (for now) |
| 14 |
- ordering patch by numbers |
| 15 |
- cleaning folder when the machine is restarted |
| 16 |
- sending the patches to the server in order |
| 17 |
- cleaning client terminal output by catching the exceptions |
| 18 |
- working on making the code for sending a unknown number of files with Werkzeug |
| 19 |
|
| 20 |
Kpatch work: |
| 21 |
- Started to make the incremental patch feature |
| 22 |
- Tested kpatch for permission issue |
| 23 |
|
| 24 |
|
| 25 |
Plan (ordered by importance): |
| 26 |
|
| 27 |
- incremental patch tracking on the client side |
| 28 |
- CVE security vulnaribility checker |
| 29 |
- dividing the repository [optional] |
| 30 |
- ebuild [optional] |
| 31 |
- documentation [optional] |
| 32 |
- modularity [optional] |
| 33 |
|
| 34 |
|
| 35 |
--------------------------------------------------- |
| 36 |
day 37 |
| 37 |
|
| 38 |
`What was my plan for today?` |
| 39 |
|
| 40 |
* testing and improving elivepatch |
| 41 |
|
| 42 |
`What i did today?` |
| 43 |
|
| 44 |
* Fix return message for cve option |
| 45 |
* Added different configuration example [4.9.30,4.10.17] |
| 46 |
* Catch gentoo-sources not available error |
| 47 |
* Catch missing livepatch errors on the client |
| 48 |
|
| 49 |
Tested kpatch with patch for kernel 4.9.30 and 4.10.17 and it worked |
| 50 |
without any problem. |
| 51 |
I checked with coverage for see which code is not used. |
| 52 |
I think we can maybe remove cve option for now as not implemented yet |
| 53 |
and we could use a modular implementation of for it, so the configuration |
| 54 |
could change. |
| 55 |
We need some documentation about elivepatch on the gentoo wiki. |
| 56 |
We need some unittest for making development more smooth and making it |
| 57 |
more simple to check the working status with github travis. |
| 58 |
|
| 59 |
I talked with kpatch creator and we got some feedback: |
| 60 |
|
| 61 |
“this project could also be used for kpatch testing :) |
| 62 |
imagine instead of just loading the .ko, the client were to kick off |
| 63 |
a series of tests and report back.” |
| 64 |
|
| 65 |
“why bother a production or tiny machine when you might have a |
| 66 |
patch-building server” |
| 67 |
|
| 68 |
|
| 69 |
`what i will do next time?` |
| 70 |
|
| 71 |
* testing and improving elivepatch |
| 72 |
|
| 73 |
--------------------------------------------------- |
| 74 |
day 38 |
| 75 |
|
| 76 |
`What was my plan for today?` |
| 77 |
|
| 78 |
* testing and improving elivepatch |
| 79 |
|
| 80 |
`What i did today?` |
| 81 |
|
| 82 |
Meeting with mentor summary |
| 83 |
|
| 84 |
What we will do next: |
| 85 |
- incremental patch tracking on the client side |
| 86 |
- CVE security vulnaribility checker |
| 87 |
- dividing the repository |
| 88 |
- ebuild |
| 89 |
- documentation [optional] |
| 90 |
- modularity [optional] |
| 91 |
|
| 92 |
Kpatch work: |
| 93 |
- Started to make the incremental patch feature |
| 94 |
- Tested kpatch for permission issue |
| 95 |
|
| 96 |
|
| 97 |
`what i will do next time?` |
| 98 |
|
| 99 |
* testing and improving elivepatch |
| 100 |
* Investigating the missing informations in the livepatch |
| 101 |
--------------------------------------------------- |
| 102 |
day 39 |
| 103 |
|
| 104 |
`What was my plan for today?` |
| 105 |
|
| 106 |
* testing and improving elivepatch |
| 107 |
|
| 108 |
`What i did today?` |
| 109 |
|
| 110 |
Meeting with mentor summary |
| 111 |
|
| 112 |
elivepatch work: |
| 113 |
- working on incremental patch features design and implementatio |
| 114 |
- putting patch files under /tmp/elivepatch (for now) |
| 115 |
- ordering patch by numbers |
| 116 |
- cleaning folder when the machine is restarted |
| 117 |
- sending the patches to the server in order |
| 118 |
- cleaning client terminal output by catching the exceptions |
| 119 |
|
| 120 |
|
| 121 |
`what i will do next time?` |
| 122 |
|
| 123 |
* testing and improving elivepatch |
| 124 |
--------------------------------------------------- |
| 125 |
day 40 |
| 126 |
|
| 127 |
`What was my plan for today?` |
| 128 |
|
| 129 |
* testing and improving elivepatch |
| 130 |
|
| 131 |
`What i did today?` |
| 132 |
|
| 133 |
Meeting with mentor summary |
| 134 |
|
| 135 |
elivepatch work: |
| 136 |
- working on incremental patch manager |
| 137 |
- cleaning client terminal output by catching the exceptions |
| 138 |
|
| 139 |
Making and Testing patch manager |
| 140 |
|
| 141 |
|
| 142 |
`what i will do next time?` |
| 143 |
|
| 144 |
* testing and improving elivepatch |
| 145 |
--------------------------------------------------- |
| 146 |
day 41 |
| 147 |
|
| 148 |
`What was my plan for today?` |
| 149 |
|
| 150 |
* working on incremental patches for elivepatch |
| 151 |
|
| 152 |
`What i did today?` |
| 153 |
|
| 154 |
elivepatch work: |
| 155 |
- working on making the code for sending a unknown number of files with Werkzeug |
| 156 |
|
| 157 |
Making and Testing patch manager |
| 158 |
|
| 159 |
|
| 160 |
`what i will do next time?` |
| 161 |
|
| 162 |
* working on the incremental patches for elivepatch |
| 163 |
|
| 164 |
-- |
| 165 |
Thanks, |
| 166 |
Alice Ferrazzi |
| 167 |
|
| 168 |
Gentoo Kernel Project Leader |
| 169 |
Mail: Alice Ferrazzi <alicef@g.o> |
| 170 |
PGP: 2E4E 0856 461C 0585 1336 F496 5621 A6B2 8638 781A |
Archives