public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: Benjamin LaHaise <bcrl@redhat.com>, Andi Kleen <ak@muc.de>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] statfs64 no longer missing
Date: Fri, 18 Oct 2002 04:31:05 +0200	[thread overview]
Message-ID: <20021018023105.GA15931@averell> (raw)
In-Reply-To: <15791.21383.361727.533851@wombat.chubb.wattle.id.au>

> --- a/arch/i386/kernel/entry.S	Fri Oct 18 10:07:29 2002
> +++ b/arch/i386/kernel/entry.S	Fri Oct 18 10:07:29 2002
> @@ -737,6 +737,8 @@
>  	.long sys_free_hugepages
>  	.long sys_exit_group
>  	.long sys_lookup_dcookie
> +	.long sys_statfs64
> +	.long sys_fstatfs64 /* 255 */

Funny. Finally filling the 8bits for syscall numbers.

> +long vfs_statfs64(struct super_block *sb, struct statfs64 *buf)
> +{
> +	struct kstatfs st;
> +	int retval;
> +
> +	retval = vfs_statfs(sb, &st);
> +	if (retval)
> +		return retval;
> +
> +	if (sizeof(*buf) == sizeof(st))
> +		memcpy(buf, &st, sizeof(st));

Don't you need to clear spare here too ?

-Andi

  parent reply	other threads:[~2002-10-18  2:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16 14:06 statfs64 missing Andi Kleen
2002-10-16 14:16 ` Trond Myklebust
     [not found]   ` <15789.64263.606518.921166@wombat.chubb.wattle.id.au>
2002-10-17  0:01     ` Andi Kleen
2002-10-17 19:41       ` Benjamin LaHaise
2002-10-18  0:19         ` [PATCH] statfs64 no longer missing Peter Chubb
2002-10-18  0:26           ` Benjamin LaHaise
2002-10-18  2:31           ` Andi Kleen [this message]
2002-10-18  3:27             ` Peter Chubb
2002-10-18  6:17           ` Andreas Dilger
2002-10-18  6:31             ` Andi Kleen
2002-10-18  6:41               ` David S. Miller

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=20021018023105.GA15931@averell \
    --to=ak@muc.de \
    --cc=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@chubb.wattle.id.au \
    --cc=trond.myklebust@fys.uio.no \
    /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