mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Phil Auld <pauld@egenera.com>
Cc: viro@math.psu.edu, marcelo@connectiva.com.br,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.19 revert block_llseek behavior to standard
Date: Mon, 12 Aug 2002 17:46:34 +0100	[thread overview]
Message-ID: <20020812174634.A10106@infradead.org> (raw)
In-Reply-To: <20020812120659.B27650@vienna.EGENERA.COM>; from pauld@egenera.com on Mon, Aug 12, 2002 at 12:06:59PM -0400

On Mon, Aug 12, 2002 at 12:06:59PM -0400, Phil Auld wrote:
> Hi Al,
> 	I think this falls under the VFS umbrella, but I may be wrong. 
> 
> Below is a fix to make block_llseek behave as specified in the Single Unix Spec. v3.
> (http://www.unix-systems.org/single_unix_specification/). It's extremely trivial but
> may have political baggage.

Have you tested when you actually seek over the size of a block device?
Stupid standards aside: what is the purpose of this?  blockdevices won't
grow bigger if you seek beyond them..

Did any Linux implementation ever follow the standard (as you rewrite
reverse)?  What's the behaviour of other unix systems when seeking
beyond the end of block devices?

  parent reply	other threads:[~2002-08-12 16:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-12 16:06 Phil Auld
2002-08-12 16:20 ` Alan Cox
2002-08-12 16:36   ` Phil Auld
2002-08-12 17:14     ` Alan Cox
2002-08-12 17:57       ` Phil Auld
2002-08-12 18:06         ` Alan Cox
2002-08-12 18:14           ` Phil Auld
2002-08-12 18:06       ` Phil Auld
2002-08-12 16:46 ` Christoph Hellwig [this message]
2002-08-12 17:14   ` Phil Auld
2002-08-13  8:13   ` Helge Hafting
     [not found] <266483518@toto.iv>
2002-08-12 22:25 ` Peter Chubb

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=20020812174634.A10106@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@connectiva.com.br \
    --cc=pauld@egenera.com \
    --cc=viro@math.psu.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

all inboxes | Powered by JetHome®