From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Neil Brown <neilb@suse.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
"J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org
Subject: Re: [REGRESSION PATCH] NFS: let NFS_V4 and NFSD_V4 enforce CRYPTO
Date: Mon, 30 Aug 2010 14:33:05 +0200 [thread overview]
Message-ID: <20100830123305.GB14459@pengutronix.de> (raw)
In-Reply-To: <20100830121022.GA14459@pengutronix.de>
On Mon, Aug 30, 2010 at 02:10:22PM +0200, Uwe Kleine-König wrote:
> On Mon, Aug 30, 2010 at 08:36:59PM +1000, Neil Brown wrote:
> > On Mon, 30 Aug 2010 10:26:18 +0200
> > Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
> >
> > > [extending Cc: to contain Neil and linux-nfs]
> > >
> > > On Fri, Aug 27, 2010 at 08:11:39AM +0200, Uwe Kleine-König wrote:
> > > > On Wed, Aug 25, 2010 at 11:05:19AM +0200, Uwe Kleine-König wrote:
> >
> > I would tend to wait more than 2 days between pings..
>
> ukl@octopus:~/gsrc/linux-2.6$ git rev-parse linus/master
> 2bfc96a127bc1cc94d26bfaa40159966064f9c8c
> ukl@octopus:~/gsrc/linux-2.6$ git grep -E CRYPTO= linus/master arch/arm/configs/ | wc -l
> 6
> ukl@octopus:~/gsrc/linux-2.6$ git grep -E NFSD?_V4 linus/master arch/arm/configs/ | wc -l
> 37
This is wrong, because the last line counts configs having both NFSD_V4
and NFS_V4 twice. There are "only" 31 that have at least one of NFSD_V4
and NFS_V4. But only one of these (at572d940hfek_defconfig) has CRYPTO
set, too.
> So I think that at least 31 arm-defconfigs don't build because of this
> issue. And as this kind of error greatly hurts automatic bisection I
> thought this to be critical enough to be a bit impatient.
To extend the test to non-ARM land:
ukl@octopus:~/gsrc/linux-2.6$ git ls-tree -r --name-only linus/master | grep defconfig | xargs grep -l -E 'CONFIG_NFSD?_V4=' | xargs grep -L CONFIG_CRYPTO= | wc -l
108
(Thinking about it again probably not all of them are broken, because
there might be other symbols selecting CRYPTO.)
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-08-30 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100825084912.GA10293@pengutronix.de>
[not found] ` <1282727119-8295-1-git-send-email-u.kleine-koenig@pengutronix.de>
[not found] ` <20100827061139.GA27851@pengutronix.de>
2010-08-30 8:26 ` [REGRESSION PATCH] NFS: let NFS_V4 and NFSD_V4 enforce CRYPTO Uwe Kleine-König
2010-08-30 10:36 ` Neil Brown
2010-08-30 12:10 ` Uwe Kleine-König
2010-08-30 12:33 ` Uwe Kleine-König [this message]
2010-08-30 13:50 ` Trond Myklebust
2010-08-30 14:36 ` Uwe Kleine-König
2010-09-01 8:52 ` [REGRESSION PATCH v2] " Uwe Kleine-König
2010-09-01 13:17 ` Trond Myklebust
2010-09-01 13:50 ` Uwe Kleine-König
2010-09-03 20:24 ` Uwe Kleine-König
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=20100830123305.GB14459@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.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