From: "J. Bruce Fields" <bfields@fieldses.org>
To: Anirban Sinha <ASinha-z4qIPS1Syiu/3pe1ocb+swC/G2K4zDHf@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfsd restart failures without /proc/fs/nfsd filesystem mounted
Date: Wed, 2 Apr 2008 18:26:11 -0400 [thread overview]
Message-ID: <20080402222611.GC16302@fieldses.org> (raw)
In-Reply-To: <DDFD17CC94A9BD49A82147DDF7D545C59D3B32-Lp/cVzEoVyb8BYCnuv3k+coc7lC+zEt2hPhL2mjWHbk@public.gmane.org>
On Wed, Apr 02, 2008 at 02:25:10PM -0700, Anirban Sinha wrote:
> >As you can see, we have an extra u_ptr member in the union (which is
> the
> >same as in the kernel: include/linux/nfsd/syscall.h).
> >
> >For experiment, I removed this member, recompiled nfs-utils and wala!
> >The kernel now gets the correct value of the server thread #.
> >
> >I am a bit puzzled by this since u_umap member already has a char* and
> I
> >think adding a void* does not change the alignment of the union.
>
>
> Indeed. Actually, by mistake, I was using the new 1.1.2 nfs-utils
> binaries and making changes in the old 1.1.0 nfs-utils source. The
> removal of the member does not change anything. What is happening is
> that an upgrade to the new 1.1.2 nfs-utils binaries solves the problem.
> I think you can reproduce the problem at your end simply by unmounting
> nfsd filesystem and using 1.1.0 nfs-utils binary.
OK! Hm, do you know which patch actually fixed this? (Is it actually
just the same problem you reported before?) On a quick skim through the
git history I'm not seeing it.
--b.
next prev parent reply other threads:[~2008-04-02 22:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 22:39 nfsd restart failures without /proc/fs/nfsd filesystem mounted Anirban Sinha
[not found] ` <DDFD17CC94A9BD49A82147DDF7D545C59D349C-Lp/cVzEoVyb8BYCnuv3k+coc7lC+zEt2hPhL2mjWHbk@public.gmane.org>
2008-04-01 21:06 ` J. Bruce Fields
2008-04-01 21:19 ` Anirban Sinha
[not found] ` <DDFD17CC94A9BD49A82147DDF7D545C59D3777-Lp/cVzEoVyb8BYCnuv3k+coc7lC+zEt2hPhL2mjWHbk@public.gmane.org>
2008-04-01 22:13 ` J. Bruce Fields
2008-04-02 19:28 ` Anirban Sinha
[not found] ` <DDFD17CC94A9BD49A82147DDF7D545C59D3A6C-Lp/cVzEoVyb8BYCnuv3k+coc7lC+zEt2hPhL2mjWHbk@public.gmane.org>
2008-04-02 21:25 ` Anirban Sinha
[not found] ` <DDFD17CC94A9BD49A82147DDF7D545C59D3B32-Lp/cVzEoVyb8BYCnuv3k+coc7lC+zEt2hPhL2mjWHbk@public.gmane.org>
2008-04-02 22:26 ` J. Bruce Fields [this message]
2008-04-02 23:06 ` Anirban Sinha
2008-04-01 21:24 ` Anirban Sinha
2008-04-01 22:48 ` Steve Dickson
[not found] ` <47F2BBDA.3080207-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-04-01 22:56 ` Anirban Sinha
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=20080402222611.GC16302@fieldses.org \
--to=bfields@fieldses.org \
--cc=ASinha-z4qIPS1Syiu/3pe1ocb+swC/G2K4zDHf@public.gmane.org \
--cc=linux-nfs@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