From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [NFS] some strangeness (at least) with linux-2.4.17-NFS_ALL patch
Date: Sat, 12 Jan 2002 03:24:59 +0100 [thread overview]
Message-ID: <15423.40571.772367.676896@charged.uio.no> (raw)
In-Reply-To: <15423.39344.864108.741338@charged.uio.no>
In-Reply-To: <20020111131528.44F8613E6@shrek.lisa.de> <15422.65459.871735.203004@charged.uio.no> <20020111191744.7A9CE1426@shrek.lisa.de> <15423.39344.864108.741338@charged.uio.no>
>>>>> " " == Trond Myklebust <trond.myklebust@fys.uio.no> writes:
> Are you sure that you didn't mess up the fixups with
> 2.4.18-pre1? That might explain things, since you would be
> messing with nfs_refresh_inode. What you need to do against
> 2.4.18-pre1 is first to revert the patch
> linux-2.4.17-fattr.dif. After that you should be able to apply
> linux-2.4.17-NFS_ALL.dif directly without any rejections...
Please also note that the version of linux-2.4.17-NFS_ALL.dif that
appeared on my site dated prior to 20th December had a bug within
nfs_refresh_inode that cause corruption of file attributes.
Is it possible that you might be using this buggy version?
Cheers,
Trond
next prev parent reply other threads:[~2002-01-12 2:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 13:15 Hans-Peter Jansen
2002-01-11 15:07 ` Trond Myklebust
2002-01-11 19:17 ` Hans-Peter Jansen
2002-01-12 2:24 ` Trond Myklebust [this message]
2002-01-12 17:01 ` [NFS] some strangeness (at least) with linux-2.4.18-NFS_ALL patch Hans-Peter Jansen
2002-01-12 18:47 ` Trond Myklebust
2002-01-12 22:40 ` Hans-Peter Jansen
2002-01-13 12:37 ` Trond Myklebust
2002-01-12 2:04 ` [NFS] some strangeness (at least) with linux-2.4.17-NFS_ALL patch Trond Myklebust
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=15423.40571.772367.676896@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=hpj@urpla.net \
--cc=linux-kernel@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 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®