From: arno@natisbad.org (Arnaud Ebalard)
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: [bisected] Weird sysctl regression
Date: Sat, 23 Aug 2008 19:13:49 +0200 [thread overview]
Message-ID: <87ljynd582.fsf@natisbad.org> (raw)
In-Reply-To: <20080823170248.GL28946@ZenIV.linux.org.uk> (Al Viro's message of "Sat, 23 Aug 2008 18:02:48 +0100")
Hi,
Al Viro <viro@ZenIV.linux.org.uk> writes:
> On Sat, Aug 23, 2008 at 06:03:33PM +0200, Arnaud Ebalard wrote:
>> > Can you reproduce it on mainline kernel
>>
>> All Linux 2.6.26 (initial and stable releases) are not affected. I am
>> currently running 2.6.26.3.
>>
>> > or bisect between the mainline and net-2.6 if mainline is OK?
>>
>> As I wrote in my previous email, bisecting net-2.6 lead me to
>> 9043476f726802f4b00c96d0c4f418dde48d1304 ([PATCH] sanitize proc_sysctl)
>> which is in the middle of a set of fs/sysctl related patches.
>>
>> I think I am missing the point on what you want me to do. Can you
>> clarify?
>
> Check the tip of Linus' git tree. Or, at least, something like -rc4.
I already tested 26.27-rc4 and even net-next-2.6 (recently released one
based on rc4 with some bug fixes). Problem is still here.
I did not already tested tip of Linus' git tree but can do it on Monday.
This might be completely unrelated but while looking at others commits
around previous one, I saw bd7b1533cd6a68c734062aa69394bec7e2b1718e
([PATCH] sysctl: make sure that /proc/sys/net/ipv4 appears before per-ns
ones). Does IPv6 need the same kind of trick ?
Cheers,
a+
next prev parent reply other threads:[~2008-08-23 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 7:18 [bisected] Weird sysctl regression Arnaud Ebalard
2008-08-23 8:49 ` Al Viro
2008-08-23 16:03 ` Arnaud Ebalard
2008-08-23 17:02 ` Al Viro
2008-08-23 17:13 ` Arnaud Ebalard [this message]
2008-08-23 18:16 ` Al Viro
2008-08-23 21:09 ` Arnaud Ebalard
2008-08-24 11:54 ` Al Viro
2008-08-24 12:53 ` Arnaud Ebalard
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=87ljynd582.fsf@natisbad.org \
--to=arno@natisbad.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).