From: Sven Eckelmann <sven@narfation.org>
To: Ruben Wisniewski <ruben@freifunk-nrw.de>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Patch which fixes a uint32overflow ; fix algorithm which was unintented changed on 2014 update
Date: Sun, 17 May 2015 11:29:23 +0200 [thread overview]
Message-ID: <4200655.6GyRK0zN7P@sven-edge> (raw)
In-Reply-To: <20150517112110.201fce11@i3.local>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
Please don't drop the mailing list when replying (unless it is actually
private conversation).
On Sunday 17 May 2015 11:21:10 Ruben Wisniewski wrote:
> > should be included:
> Since the overflow-bug seem to be is since epoch, the patch have to be
> applied to all versions.
I am talking about the part which you described yourself as regression. But I
agree that the overflow bug is in there since the beginning of the gateway
code.
> But I think batman-adv 2013.x is that old that
> nobody is using it anymore or kernels with that version. So we just
> have to fix all 2014.x versions.
There is a stable branch for Linux 2.6.32.x. Linux 2.6.32 came out 2009. So it
is possible that David Miller decides to submit the overflow patch to stable
for 2.6.32. This is not in our jurisdiction. The same may be the case for the
regression - but then somebody (David Miller/stable team) must know how severe
the problem is and when it was introduced.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-05-17 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-16 20:15 [B.A.T.M.A.N.] Patch which fixes a uint32overflow ; fix algorithm which was unintented changed on 2014 update Ruben Wisniewski
2015-05-16 22:11 ` Sven Eckelmann
2015-05-17 8:26 ` Sven Eckelmann
[not found] ` <20150517112110.201fce11@i3.local>
2015-05-17 9:29 ` Sven Eckelmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4200655.6GyRK0zN7P@sven-edge \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=ruben@freifunk-nrw.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox