From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Alexey Dobriyan <adobriyan@gmail•com>
Cc: linux-next@vger•kernel.org, "Eric W. Biederman" <ebiederm@xmission•com>
Subject: linux-next: proc tree build failure
Date: Thu, 20 Nov 2008 17:24:25 +1100 [thread overview]
Message-ID: <20081120172425.135c8cf8.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
Hi Alexey,
Today's linux-next build (x86_64 allmodconfig) failed like this:
security/selinux/hooks.c: In function 'selinux_proc_get_sid':
security/selinux/hooks.c:1182: error: 'struct super_block' has no member named 'type'
security/selinux/hooks.c:1183: error: 'struct super_block' has no member named 'type'
security/selinux/hooks.c:1189: error: too few arguments to function 'memcpy'
Caused by commit e23b822350796e690a46873058d220878a18564c ("proc:
make /proc/net it's own filesystem"). This has clearly never been
compiled with CONFIG_PROC_FS set! I have dropped the proc tree for today.
Much better testing is required - this should never have been submitted
to linux-next in this state.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-11-20 6:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 6:24 Stephen Rothwell [this message]
2008-11-20 8:43 ` linux-next: proc tree build failure Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2009-03-30 6:43 Stephen Rothwell
2009-01-23 6:15 Stephen Rothwell
2009-01-23 7:09 ` Cyrill Gorcunov
2009-01-23 18:48 ` Alexey Dobriyan
2009-01-23 19:26 ` Cyrill Gorcunov
2009-01-23 19:41 ` Cyrill Gorcunov
2009-01-23 20:26 ` Cyrill Gorcunov
2008-11-24 7:15 Stephen Rothwell
2008-11-28 8:05 ` Alexey Dobriyan
2008-11-28 9:00 ` David Miller
2008-11-28 10:25 ` David Miller
2008-11-10 5:29 Stephen Rothwell
2008-11-10 5:53 ` Alexey Dobriyan
2008-11-10 7:36 ` Ingo Molnar
2008-10-21 7:21 Stephen Rothwell
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=20081120172425.135c8cf8.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=adobriyan@gmail$(echo .)com \
--cc=ebiederm@xmission$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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