linux-kernel - Re: [PATCH] seq_file: Fix seq_putc() to be consistent with seq

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]

Message-ID: <1412008235.4302.31.camel@joe-AO725>
Date:	Mon, 29 Sep 2014 09:30:35 -0700
From:	Joe Perches <joe@...ches.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Al Viro <viro@...IV.linux.org.uk>, Petr Mladek <pmladek@...e.cz>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] seq_file: Fix seq_putc() to be consistent with
 seq_puts()

On Mon, 2014-09-29 at 12:15 -0400, Steven Rostedt wrote:
> On Mon, 29 Sep 2014 09:08:01 -0700
> Joe Perches <joe@...ches.com> wrote:
> 
> > On Mon, 2014-09-29 at 16:47 +0100, Al Viro wrote:
> > > On Mon, Sep 29, 2014 at 04:41:22PM +0200, Petr Mladek wrote:
> > > > Hmm, this inconsistency seems to be in more functions. I would divide
> > > > it into three categories:
> > []
> > > No.  _Any_ caller that decides to report that error to its caller is fucking
> > > broken.  We had some cases like that.
> > []
> > > And let's make seq_printf and friends return void.  Any breakage we miss
> > > on grep will be caught by compiler.  Enough is enough.
> > 
> > https://lkml.org/lkml/2013/12/11/8
> > 
> 
> Since you like posting links:
> 
> https://lkml.org/lkml/2013/12/11/76
> 
> If you want to resurrect your patches, go ahead. I'll pull them into my
> list. Probably should rename seq_overflow() to seq_is_full(), which
> makes it sound less of an error.
> 
> And as Al noted, only fix what's there (just the places that check the
> return values). Don't add anything else.

I did that too

https://lkml.org/lkml/2013/12/11/713

Then I gave up.

--
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/