linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Theodore Tso <tytso@mit.edu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jens Axboe <jens.axboe@oracle.com>,
	Arjan van de Ven <arjan@infradead.or
Cc: Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [PATCH] fs: Correct SuS compliance for open of large file without options
Date: Thu, 27 Sep 2007 20:21:35 -0700	[thread overview]
Message-ID: <20070928032135.GA23543@kroah.com> (raw)
In-Reply-To: <20070927231927.GE8688@thunk.org>

On Thu, Sep 27, 2007 at 07:19:27PM -0400, Theodore Tso wrote:
> On Thu, Sep 27, 2007 at 02:34:45PM -0700, Greg KH wrote:
> > Ok, how then should I advertise this better?  What can we do better to
> > help userspace programmers out in this regard?
> 
> Would you accept a patch which causes the deprecated sysfs
> files/directories to disappear, even if CONFIG_SYS_DEPRECATED is
> defined, via a boot-time parameter?

As discussed in the kernel summit talk about this very topic, Kay is
working on a patch to do just that :)

> Many people and distros are
> likely to keep CONFIG_SYS_DEPRECATED defined just our of paranoia that
> things might break.  Doing a quick google, I note that Fedora has been
> going back and forth of turning it off, watching things break, and
> then turning it back on.  The latest time, the changelog said:
> 
> * Fri Jan 26 23:00:00 2007 Bill Nottingham <notting{%}redhat{*}com>
> 
>     - turn on CONFIG_SYSFS_DEPRECATED so that things actually work. *sigh*
> 
> (and I've checked, Fedora's CVS still has CONFIG_SYSFS_DEPRECATED
> defined; it's not just Debian at fault here.)

That's odd, SuSE and Gentoo have been working for quite some time just
fine with that option disabled :)

thanks,

greg k-h

  parent reply	other threads:[~2007-09-28  3:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27 13:29 [PATCH] fs: Correct SuS compliance for open of large file without options Alan Cox
2007-09-27 14:01 ` Arjan van de Ven
2007-09-27 14:19   ` Alan Cox
2007-09-27 14:35     ` Jens Axboe
2007-09-27 14:44       ` Alan Cox
2007-09-27 15:08         ` Jens Axboe
2007-09-27 15:19           ` Alan Cox
2007-09-27 15:59             ` Theodore Tso
2007-09-27 17:23               ` Andrew Morton
2007-09-27 17:59                 ` Greg KH
2007-09-27 18:37                   ` Theodore Tso
2007-09-27 18:45                     ` Matthew Wilcox
2007-09-27 21:34                     ` Greg KH
2007-09-27 22:27                       ` Kyle Moffett
2007-09-27 23:11                         ` Greg KH
2007-09-27 23:19                       ` Theodore Tso
2007-09-27 23:28                         ` Matthew Wilcox
     [not found]                         ` <20070927232857.GA12049@parisc-linux.org>
2007-09-28  2:21                           ` Theodore Tso
2007-09-28  3:22                           ` Greg KH
2007-09-28  3:21                         ` Greg KH [this message]
2007-09-27 23:41               ` Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070928032135.GA23543@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.or \
    --cc=jens.axboe@oracle.com \
    --cc=kay.sievers@vrfy.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).