linux-kernel - Re: [2.6.27-rc4-git5] ipv4: sysctl fixes causes "cannot open /proc/sys/net/ipv4/route/flush"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 26 Aug 2008 20:05:15 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Rufus & Azrael <rufus-azrael@...ericable.fr>
Cc:	Linux-kernel Mailing List <linux-kernel@...r.kernel.org>,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: [2.6.27-rc4-git5] ipv4: sysctl fixes causes "cannot open
	/proc/sys/net/ipv4/route/flush"

On Tue, Aug 26, 2008 at 07:14:50PM +0200, Rufus & Azrael wrote:
> Rufus & Azrael wrote:
>> Hi Al and David,
>>
>>
>> After building the fresh 2.6.27-rc4-git5 kernel with your patch in commit 
>> 2f4520d35d89ca6c5cd129c38e3b11f0283b7d1b, I have this error on boot :
>>
>>> Cannot open "/proc/sys/net/ipv4/route/flush"
>> but networking works fine.
>>
>> Do I modify something in my sysctl.conf file ? (see attached).
>>
>> Thanks for your explanations,
>>
>> Regards.
>>
>>
>>
> Ok, perhaps is it a regression of your previous patches in commits 
> eeb61f719c00c626115852bbc91189dc3011a844 and 
> 6f9f489a4eeaa3c8a8618e078a5270d2c4872b67 (
> net: missing bits of net-namespace / sysctl)

I'm just about to fall down at the moment, will look into that once I get
some sleep.  In the meanwhile, .config might be useful...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/