All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Yoav Zach <yoav_zach@yahoo.com>
Cc: torvalds@osdl.org, lkml <linux-kernel@vger.kernel.org>,
	Yoav Zach <yoav.zach@intel.com>
Subject: Re: [PATCH]: Don't force O_LARGEFILE for 32 bit processes on ia64 - 2.6.12-rc3
Date: Tue, 10 May 2005 16:47:17 +1000	[thread overview]
Message-ID: <20050510064717.GA17819@krispykreme> (raw)
In-Reply-To: <20050509214710.419.qmail@web50610.mail.yahoo.com>


Hi,

> In ia64 kernel, the O_LARGEFILE flag is forced when
> opening a file. This is problematic for execution of
> 32 bit processes, which are not largefile aware, either
> by SW emulation or by HW execution.
> For such processes, the problem is two-fold:
> 1) When trying to open a file that is larger than 4G
>    the operation should fail, but it's not
> 2) Writing to offset larger than 4G should fail, but
>    it's not
> 
> The proposed patch takes advantage of the way 32 bit
> processes are identified in ia64 systems. Such 
> processes have PER_LINUX32 for their personality. With
> the patch, the ia64 kernel will not enforce the O_LARGEFILE
> flag if the current process has PER_LINUX32 set.
> The behavior for all other architectures remains unchanged.

A 32 bit application should not be using the native open routine. 

Sounds like you have a 64bit emulator running 32bit applications. The
other 64bit architectures need to be audited to make sure the
PER_LINUX32 flag is safe to use here.

Anton

  parent reply	other threads:[~2005-05-10  6:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 21:47 [PATCH]: Don't force O_LARGEFILE for 32 bit processes on ia64 - 2.6.12-rc3 Yoav Zach
2005-05-10  1:45 ` Jeff Garzik
2005-05-10  5:15   ` tony.luck
2005-05-10  6:47 ` Anton Blanchard [this message]
2005-05-10 16:15   ` tony.luck
  -- strict thread matches above, loose matches on Subject: below --
2005-05-10 21:45 Zach, Yoav

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=20050510064717.GA17819@krispykreme \
    --to=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=yoav.zach@intel.com \
    --cc=yoav_zach@yahoo.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.