You are not logged in.
Hello all,
Not really a general Linux newbie, but a newbie on kernel patch management and specifically I have no idea how upstream/downstream/sidestream(?) patches might end up in the kernel... :-)
I am experiencing exactly the issue mentioned on https://bugzilla.redhat.com/show_bug.cgi?id=1204512
Now, I will try and find time tonight to try and manually patch the kernel (not the first time there), but I was wondering: how/if/when can a patch like the one mentioned on the RH bugzilla end up in the kernel as we receive it in Arch' repositories?
Thx,
Bruno
Offline
Dates from January it seems, maybe better reference from kernel.org itself:
https://bugzilla.kernel.org/show_bug.cgi?id=90901
So, how/when/if would that end up in Arch's main kernel? :-)
Offline
I'm also affected by this issue, koproliet did you find any answer on this?
Offline
I'm also affected by this issue, koproliet did you find any answer on this?
Man, this has been bugging the hell out of me for the longest time. Thought it was just me for some stupid reason. Based on the fact that there is a patch in the bug in kernel.org, I'm guessing this will make its way down to our kernel at some point?
Offline
I did not find an answer on it no.
How and where do I request this to be included in the current (4.02 by now) to the kernel in the core repository... ?
It is not easy to figure out if 4.02 has the bugfix upstream (was in 3.19 already but not in our core repository kernel, also not sure why).
Should trickle down eventually I assume.
Last edited by koproliet (2015-04-28 14:02:34)
Offline
I haven't tried linux-4.0 from testing yet, but I have verified that the fix in the bugzilla.kernel.org patch appears in the 4.0 mainline source. So I too am keeping my fingers crossed.
Linux User #353 - SLS -> Slackware -> Red Hat -> Mandrake -> Fedora -> Arch
Offline
How do you find/verify this? Maybe I am missing something, but cannot really "link" the bug-id to the kernel changes/diffs?
Tried searching https://git.kernel.org/cgit/linux/kerne … .git/diff/ for changes related to the change proposed in the patch, "diff --git a/drivers/net/tun.c b/drivers/net/tun.c" so anything on tun.c but nothing.
You searched inside the complete source tarball? :-) Is that the only/best way to check if a specific patch is included? :-)
Just want to know how to figure this out myself in the future.
Last edited by koproliet (2015-04-28 16:46:53)
Offline
Just tested today with kernel 4.0-2 in [testing] and was able to connect and ping hosts on private VPN so looks like the fix made it's way down to us. ![]()
Offline
How do you find/verify this? Maybe I am missing something, but cannot really "link" the bug-id to the kernel changes/diffs?
...
Just want to know how to figure this out myself in the future.
I don't know how to link to the specific patch either (my git-fu is not that good), but in this case, since the patch was a one-liner, I just went to the kernel.org website and browsed the stable 4.0 source.
Specifically (sorry if this is too obvious, but you asked):
Go to kernel.org, click on the "browse" button on the version you want to see. Then select "tree" to see the source directory itself. Then drill down to drivers/net/tun.c and find the function where the change was to happen. (This is safer than line numbers specifically, since there may have been other patches that cause line offsets.) The change was indeed made in the 4.0 source, so I was optimistic that the fix would really happen.
Since cris9288 reported success, and 4.0.1 has just been pushed out of testing, I'm hoping this saga is over. (Too much work for me to do the update just yet, hopefully by tomorrow.)
Cheers.
Linux User #353 - SLS -> Slackware -> Red Hat -> Mandrake -> Fedora -> Arch
Offline
It is resolved! :-)
(If you run vmware player with windows under it because your employer makes you use some win applications, like me, note https://bbs.archlinux.org/viewtopic.php?id=196778 when upgrading though).
Offline