[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150826163621.28d7990a@gandalf.local.home>
Date: Wed, 26 Aug 2015 16:36:21 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Sean Fu <fxinrong@...il.com>
Cc: Austin S Hemmelgarn <ahferroin7@...il.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
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 Wed, 26 Aug 2015 23:48:01 +0800
Sean Fu <fxinrong@...il.com> wrote:
> > Defending the patch, I can't imagine any user space code expecting the
> > current behavior. The current behavior is that if you write "1\0" it
> > will error out instead of accepting the "1". I can't come up with a
> > scenario that would require userspace to expect "1\0" to fail. Can you?
> Thanks
Although, with the current patch, would "1\02" fail? It should.
-- Steve
--
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