[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9CF68C3D-499C-4AFC-B890-BA5ECA284347@xmission.com>
Date: Mon, 24 Aug 2015 20:24:53 -0600
From: "Eric W. Biederman" <ebiederm@...ssion.com>
To: Sean Fu <fxinrong@...il.com>, Steven Rostedt <rostedt@...dmis.org>
CC: Andrey Ryabinin <ryabinin.a.a@...il.com>,
Ulrich Obergfell <uobergfe@...hat.com>,
Prarit Bhargava <prarit@...hat.com>,
Eric B Munson <emunson@...mai.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Johannes Weiner <hannes@...xchg.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Don Zickus <dzickus@...hat.com>,
Heinrich Schuchardt <xypron.glpk@....de>,
David Rientjes <rientjes@...gle.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kernel/sysctl.c: If "count" including the terminating byte '\0' the write system call should retrun success.
On August 24, 2015 6:57:57 PM MDT, Sean Fu <fxinrong@...il.com> wrote:
>An application from HuaWei which works fine on 2.6 encounters this
>issue on 3.0 or later kernel.
My sympathies. Being stuck with a 3rd party application you can barely talk about that has been broken for 5years and no one reported it.
Ordinarily we would fix a regression like this. As it has been 5years the challenge now is how do we tell if there are applications that depend on the current behavior.
Before we can change the behavior back we need a convincing argument that we won't cause a regression in another application by making the change.
I do not see how such an argument can be made. So you have my sympathies but I do not see how we can help you.
Eric
--
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/
Powered by blists - more mailing lists