From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [PATCH v4] remove no longer use of pdflush interface Date: Wed, 6 Jun 2012 15:50:56 -0700 Message-ID: <20120606155056.72a6a2b5.akpm@linux-foundation.org> References: <1338989888-3480-1-git-send-email-liwp.linux@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Fengguang Wu , Rob Landley , Alexander Viro , "Eric W.Biederman" , Lucas De Marchi , "David S. Miller" , Jan Kara , Mel Gorman , Minchan Kim , James Morris , Ingo Molnar , Michel Lespinasse , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Gavin Shan , Wanpeng Li To: Wanpeng Li Return-path: In-Reply-To: <1338989888-3480-1-git-send-email-liwp.linux@gmail.com> Sender: linux-doc-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, 6 Jun 2012 21:38:08 +0800 Wanpeng Li wrote: > From: Wanpeng Li > > Since per-BDI flusher introduced to linux 2.6, pdflush mechanism is not > used any more. But the old interface of pdflush exported in/proc/sys/vm/ > is still there. In order to take attention to back-compatibility issues, > printk warning information and return -ENOSYS to notice the users the > interface is removed. > > ... > > +/* notice associated proc obsoleted */ This comment is pretty meaningless - I suggest simply removing it. > +int pdflush_proc_obsolete(struct ctl_table *table, int write, > + void __user *buffer, size_t *lenp, loff_t *ppos) > +{ > + printk_once(KERN_WARNING "%s exported in /proc is scheduled for removal\n", > + table->procname); > + return -ENOSYS; > +} No, this immediately breaks /proc/sys/vm/nr_pdflush_threads users. To preserve back-compatibility we should copy "0\n" out to userspace and return 2. > +EXPORT_SYMBOL(pdflush_proc_obsolete); This export isn't needed?