From: Dmitry Torokhov <dtor@vmware.com>
To: linux-kernel@vger.kernel.org
Cc: Bryan Schumaker <bjschuma@netapp.com>,
Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: 2.6.39-rc1 regression: NFS - unable to mount some shares (bisected)
Date: Wed, 30 Mar 2011 13:38:23 -0700 [thread overview]
Message-ID: <20110330203823.GA3228@dtor-ws.eng.vmware.com> (raw)
Hi,
The following commit appears to the open preventng me from mounting some
of my NFS shares (not all, of them, just some):
8f70e95f9f4159184f557a1db60c909d7c1bd2e3 is the first bad commit
commit 8f70e95f9f4159184f557a1db60c909d7c1bd2e3
Author: Bryan Schumaker <bjschuma@netapp.com>
Date: Thu Mar 24 17:12:31 2011 +0000
NFS: Determine initial mount security
When sec=<something> is not presented as a mount option,
we should attempt to determine what security flavor the
server is using.
Signed-off-by: Bryan Schumaker <bjschuma@netapp.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Here is the bisect log:
[dtor@dtor-ws linus]$ git bisect log
git bisect start
# good: [4bbba111d94781d34081c37856bbc5eb33f6c72a] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6
git bisect good 4bbba111d94781d34081c37856bbc5eb33f6c72a
# bad: [0ce790e7d736cedc563e1fb4e998babf5a4dbc3d] Linux 2.6.39-rc1
git bisect bad 0ce790e7d736cedc563e1fb4e998babf5a4dbc3d
# good: [e285c1746accb80620e511f9c72e9893beeedc0e] Merge branch 'drm-core-next' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6
git bisect good e285c1746accb80620e511f9c72e9893beeedc0e
# bad: [8d49a77568d1105ff3e64aec484dac059f54824e] Merge branch 'for-2.6.39/drivers' of git://git.kernel.dk/linux-2.6-block
git bisect bad 8d49a77568d1105ff3e64aec484dac059f54824e
# bad: [5aafdea448fb86412a6f8e46df518c1545d32436] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6
git bisect bad 5aafdea448fb86412a6f8e46df518c1545d32436
# bad: [9458ea567a72ebd3852c2d764d32c0f2fb61d0df] MIPS: IP22/IP28: Convert to new irq_chip functions
git bisect bad 9458ea567a72ebd3852c2d764d32c0f2fb61d0df
# good: [ae005cbed12d0b340b04b59d6f5c56e710b3895d] Merge branch 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4
git bisect good ae005cbed12d0b340b04b59d6f5c56e710b3895d
# bad: [1685f3b158a244d4f6e205e67c84483fffcb2d9f] MIPS: SMTC: Move declaration of smtc_init_secondary to <asm/smtc.h>.
git bisect bad 1685f3b158a244d4f6e205e67c84483fffcb2d9f
# good: [988b6dceb0ae6d642587c8594529b94f6be0c5ea] NFSv4.1: remove GETATTR from ds commits
git bisect good 988b6dceb0ae6d642587c8594529b94f6be0c5ea
# good: [35124a0994fc02545b14b9fa3aad000b3331f1c0] Cleanup XDR parsing for LAYOUTGET, GETDEVICEINFO
git bisect good 35124a0994fc02545b14b9fa3aad000b3331f1c0
# bad: [8f70e95f9f4159184f557a1db60c909d7c1bd2e3] NFS: Determine initial mount security
git bisect bad 8f70e95f9f4159184f557a1db60c909d7c1bd2e3
# good: [7c5130588d691a3b34d02312f1bd1b6d56fe0100] NFS: lookup supports s alternate client
git bisect good 7c5130588d691a3b34d02312f1bd1b6d56fe0100
# good: [7ebb931598cd95cccea10d4bc4c0123a464ea565] NFS: use secinfo when crossing mountpoints
git bisect good 7ebb931598cd95cccea10d4bc4c0123a464ea565
next reply other threads:[~2011-03-30 20:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 20:38 Dmitry Torokhov [this message]
2011-03-30 21:03 ` 2.6.39-rc1 regression: NFS - unable to mount some shares (bisected) Bryan Schumaker
-- strict thread matches above, loose matches on Subject: below --
2011-03-30 22:31 Dmitry Torokhov
2011-03-31 16:23 ` Dmitry Torokhov
2011-03-31 16:50 ` Dmitry Torokhov
2011-03-31 17:15 ` Bryan Schumaker
2011-03-31 17:19 ` Dmitry Torokhov
2011-03-31 18:53 ` Bryan Schumaker
2011-03-31 22:11 ` Dmitry Torokhov
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=20110330203823.GA3228@dtor-ws.eng.vmware.com \
--to=dtor@vmware.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bjschuma@netapp.com \
--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 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.