Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Maciej Soltysiak <maciej@soltysiak.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] A stable cerowrt release in sight
Date: Mon, 19 May 2014 11:57:53 +0200	[thread overview]
Message-ID: <A6633896-9355-43FB-9D21-BF98FBCCF7E7@gmx.de> (raw)
In-Reply-To: <CAMZR1YCqp69BJW73P=+OxkGzj7KLbit2U0LWNa=8EHXg_ttR3g@mail.gmail.com>

Hi Maciej, hi list,

\
On May 19, 2014, at 09:30 , Maciej Soltysiak <maciej@soltysiak.com> wrote:

> On Sun, May 18, 2014 at 5:29 PM, Dave Taht <dave.taht@gmail.com> wrote:
>> On Sun, May 18, 2014 at 6:48 AM,  <Valdis.Kletnieks@vt.edu> wrote:
>>> On Thu, 15 May 2014 23:36:11 -0700, Dave Taht said:
>>> root@bogon-gateway-1:~# uname -a
>>> Linux bogon-gateway-1 3.10.36 #1 Fri May 16 01:00:30 PDT 2014 mips GNU/Linux
> Noticed the same after upgrade yesterday.

	Note 3.10.40-5 is out and sports a shiny 3.10.40 kernel ;) (Installed yesterday, seems to work, but only lightly tested; did not expose 11an for the 5GHz radio or allow HT40 from the GUI, copying the relevant lines from /etc/config/wireless both made 40MHz wifi work again and exposed the settings in the GUI; I seem to recall that this was reported on the openwrt list as well, so is not a cerowrt specific issue...)

> BTW. sysupgrade didn't preserver a single setting, is that expected?
> Was upgrading form 3.10.28 or something.

	INteresting question, this could be related to the constant flux in openwrt trunk, or could just be a plain bug there. (Just as the inability of keeping gthe settings while sys upgrading from the GUI was an openwrt bug, that got fixed there...)

> 
>> (it is the patch, not the kernel, that is important)
> Well, if you look closely the 3.10.40 contains a bugfix for
> n_tty_write() : CVE-2014-0196

	This looks like a local issue only, since the only local user on cerowrt is root I do not think that this really affects us.

best regards
	sebastian

> That particular kernel might be important. Sorry for my ignorance, but
> are we affected?
> 
> Best regards,
> Maciej Soltysiak
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


  reply	other threads:[~2014-05-19  9:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16  6:36 Dave Taht
2014-05-16 19:59 ` Török Edwin
2014-05-16 20:54   ` Dave Taht
2014-05-17  6:54 ` Valdis.Kletnieks
2014-05-18  1:15   ` Aristar
2014-05-18 13:48 ` Valdis.Kletnieks
2014-05-18 15:29   ` Dave Taht
2014-05-19  7:30     ` Maciej Soltysiak
2014-05-19  9:57       ` Sebastian Moeller [this message]
2014-05-19 16:29         ` Dave Taht
2014-05-19 17:49           ` Sebastian Moeller

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=A6633896-9355-43FB-9D21-BF98FBCCF7E7@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=maciej@soltysiak.com \
    /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