All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] utime emulation
Date: Tue, 06 Aug 2002 20:23:38 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905918@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905917@msgid-missing>

>>>>> On Tue, 6 Aug 2002 12:01:15 -0700, "Wichmann, Mats D" <mats.d.wichmann@intel.com> said:

  Mats> I'm finding that utime(filename, NULL) doesn't follow specs -
  Mats> this comes up in plodding through the LSB certification test
  Mats> suite.

  Mats> For example, if the process does not own the file but has
  Mats> write permission, the above referenced call should succeed but
  Mats> fails with EPERM.

  Mats> utime() is emulated on Itanium: in the kernel, fs/open.c
  Mats> doesn't have a sys_utime routine if __ia64__ or alpha; the
  Mats> emulation comes from glibc's sysdeps/unix/utime.c but appears
  Mats> to be bogus.  The problem is that if the second argument to
  Mats> utime is NULL the emulation code does some work to build up a
  Mats> "struct timeval" array as expected by utimes(), and passes
  Mats> that off, instead of passing NULL... and so the proper checks
  Mats> in the NULL case don't get done by the kernel.

  Mats> I guess this is a query to see if anyone on this list knows
  Mats> anything about this code.  Is this just a glibc problem, or
  Mats> should Itanium go back to providing the non-emulated utime
  Mats> routine like nearly all the other arch's do (and so this
  Mats> emulation code is not run).

Please report this as a glibc bug.

	--david


  reply	other threads:[~2002-08-06 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06 19:01 [Linux-ia64] utime emulation Wichmann, Mats D
2002-08-06 20:23 ` David Mosberger [this message]
2002-08-06 20:40 ` Andreas Schwab

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=marc-linux-ia64-105590701905918@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    /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.