linux-kernel - Re: [-mm patch] #if 0 mm/backing-dev.c:congestion_wait

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] [day] [month] [year] [list]

Message-ID: <9a8748490706150831o7e8de78cq9f612564d1c5ddb0@mail.gmail.com>
Date:	Fri, 15 Jun 2007 17:31:37 +0200
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"Adrian Bunk" <bunk@...sta.de>
Cc:	"Peter Zijlstra" <a.p.zijlstra@...llo.nl>,
	"Trond Myklebust" <trond.myklebust@....uio.no>,
	linux-kernel@...r.kernel.org
Subject: Re: [-mm patch] #if 0 mm/backing-dev.c:congestion_wait_interruptible()

On 13/06/07, Adrian Bunk <bunk@...sta.de> wrote:
> On Tue, Jun 12, 2007 at 02:40:06PM +0200, Jesper Juhl wrote:
> > On 12/06/07, Adrian Bunk <bunk@...sta.de> wrote:
> >> congestion_wait_interruptible() is no longer used.
> >>
> > Remind me again why it is that we add all these  #if 0  blocks instead
> > of simply removing the unused code?
> >
> > It's just creating a janitorial task to go and remove all the #if 0
> > bits at a later time, seems like pointless churn to me. If the code
> > needs to go, let's just get rid of it in one go instead of two.
>
> The #if 0 also handles all "I want to use this code in 6 months"
> comments that might come (and in some rare cases it even gets used
> later).
>
Well, if it is going to be used in 6 months it's just as easy to add
the code back at that point as it is to remove the  #if 0  bits. Or
simply not remove it in the first place - if it's going to be used in
6 months, all we gain from  #if 0  is slightly smaller binary size for
6 months ... a bit pointless don't you think?

> My primary intention is to remove dead code from bloating the kernel
> image, and this way the probability of patch acceptance is higher.
>
I have no objections to removing dead code. That's a fine objective.
My only concern is that eventually we'll be left with a mountain of
code inside  #if 0  that noone ever cleans up.

I guess I could start grep'ing the surce for "#if 0" at regular
intervals and removing any instances that were added >6months ago...
Something inside me just screams that I shouldn't have to :-)

-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
-
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/