public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>,
	"J. Bruce Fields" <bfields@fieldses.org>
Cc: Meelis Roos <mroos@linux.ee>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-nfs@vger.kernel.org
Subject: Re: regression: am-utils stopped working in 2.6.25-rc*
Date: Wed, 02 Apr 2008 10:53:36 +0300	[thread overview]
Message-ID: <47F33B80.1070508@panasas.com> (raw)
In-Reply-To: <1207088063.13443.22.camel@heimdal.trondhjem.org>

On Apr. 02, 2008, 1:14 +0300, Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> On Tue, 2008-04-01 at 17:07 -0400, J. Bruce Fields wrote:
>> On Fri, Mar 28, 2008 at 03:20:18PM +0200, Meelis Roos wrote:
>>> Current 2.6.25-rc* kernels have broken am-utils (NFS-based automounter) 
>>> support. No error messages, just "no such file or directory" when trying 
>>> to enter /net/anotherhostname. Just tried 2.6.24 and that worked fine. 
>>> am-utils is the latest in Debian unstable, 6.1.5-9.
>>>
>>> Earliest 2.6.25-rc currently tested was 2.6.25-rc3+git as of 20080304. 
>>> This version reports 
>>> Invalid hostname "pid3477@koiott:/net" in NFS lock request
>>> into dmesg and am-utils does not work.
>>>
>>> 2.6.25-rc4+git as of 20080310 and later ones do not show this message 
>>> but am-utils does still not work.
>>>
>>> Will try bisecting it further.
>> Have you figured out anything more?  Can strace show exactly which
>> system call is  failing?
> 
> See the bugzilla report:
>   http://bugzilla.kernel.org/show_bug.cgi?id=10349

FWIW, I've already opened this bug on am-utils's bugzilla:
https://bugzilla.am-utils.org/show_bug.cgi?id=612

I updated it with the info on this message.

Benny

> 
> I'm still waiting to hear back from Meelis, but to me this looks like an
> am-utils bug.
> 
> AFAICS, am-utils advertises a binary NFS mount structure version of '6',
> to the mount() syscall, but internally they only initialise the
> equivalent of a version '4' structure.
> When
>      http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=f9c3a3802119a2d30f3e4a69aef30a81e09d0209
> was merged, then this failure to initialise the selinux 'context' field
> causes mount() to return an EINVAL.
> 
> Cheers
>   Trond
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2008-04-02  7:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 13:20 regression: am-utils stopped working in 2.6.25-rc* Meelis Roos
2008-04-01 21:07 ` J. Bruce Fields
2008-04-01 22:14   ` Trond Myklebust
2008-04-02  7:53     ` Benny Halevy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-03 22:49 2.6.25-rc8-git2: Reported regressions from 2.6.24 Rafael J. Wysocki
2008-04-03 23:22 ` regression: am-utils stopped working in 2.6.25-rc* Rafael J. Wysocki
2008-04-04  6:15   ` Meelis Roos

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=47F33B80.1070508@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mroos@linux.ee \
    --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