All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 11800] building SES support fails w/ gcc-3.4.5
Date: Wed, 22 Oct 2008 13:31:57 -0700 (PDT)	[thread overview]
Message-ID: <20081022203157.B9AF2108047@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-11800-11613@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=11800





------- Comment #3 from anonymous@kernel-bugs.osdl.org  2008-10-22 13:31 -------
Reply-To: akpm@linux-foundation.org

On Wed, 22 Oct 2008 15:43:05 -0400
Marc Bejarano <beej@alum.mit.edu> wrote:

> At 18:52 10/21/2008, Andrew Morton wrote:
>  >On Tue, 21 Oct 2008 11:36:12 -0700 (PDT)
>  >bugme-daemon@bugzilla.kernel.org wrote:
>  >
>  >> http://bugzilla.kernel.org/show_bug.cgi?id=11800
>  >>
>  >>            Summary: building SES support fails w/ gcc-3.4.5
>  >>            Product: SCSI Drivers
>  >>            Version: 2.5
>  >>      KernelVersion: 2.6.27.1
>  >>           Platform: All
>  >>         OS/Version: Linux
>  >>               Tree: Mainline
>  >>             Status: NEW
>  >>           Severity: normal
>  >>           Priority: P1
>  >>          Component: Other
>  >>         AssignedTo: scsi_drivers-other@kernel-bugs.osdl.org
>  >>         ReportedBy: bugzilla.kernel.org@beej.org
>  >>
>  >>
>  >> [beej@dell ~]$ cat /etc/redhat-release
>  >> CentOS release 4.3 (Final)
>  >> [beej@dell ~]$ rpm -qf `which gcc`
>  >> gcc-3.4.5-2
>  >> [beej@dell linux-2.6.27.1]$ diff .config .config.old
>  >> 4c4
>  >> < # Tue Oct 21 14:07:00 2008
>  >> ---
>  >> > # Thu Oct 16 17:54:42 2008
>  >> 1006c1006
>  >> < # CONFIG_SCSI_ENCLOSURE is not set
>  >> ---
>  >> > CONFIG_SCSI_ENCLOSURE=m
>  >>
>  >> using .config.old,
>  >> [beej@dell linux-2.6.27.1]$ make
>  >> <snip>
>  >> Kernel: arch/x86/boot/bzImage is ready  (#2)
>  >>   Building modules, stage 2.
>  >>   MODPOST 668 modules
>  >> ERROR: "__you_cannot_kmalloc_that_much" [drivers/scsi/ses.ko] undefined!
>  >> make[1]: *** [__modpost] Error 1
>  >> make: *** [modules] Error 2
>  >>
>  >
>  >That's weird.  It means that we did a kmalloc(N, ...) where the value
>  >of N is known at compile time, and N is too large.
>  >
>  >But I can find no such kmalloc/kzalloc calls in ses.c.  It might be gcc
>  >bustage - we've seen that before.
>  >
>  >Please do
>  >
>  >	make drivers/scsi/ses.s
>  >
>  >then have a look in drivers/scsi/ses.s and see which function is
>  >emitting a call to __you_cannot_kmalloc_that_much.  Or email me
>  >drivers/scsi/ses.s and I'll take a look.
> 
> attached
> 

OK, it's here:

        buf = kmalloc(vpd_len, GFP_KERNEL);

it's a gcc bug.

Please see if you can find some way to make it go away - perhaps change
vpd_len's type to `int', things like that.

Or use a different compiler version :(


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2008-10-22 20:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21 18:36 [Bug 11800] New: building SES support fails w/ gcc-3.4.5 bugme-daemon
2008-10-21 22:52 ` Andrew Morton
     [not found]   ` <200810221943.m9MJh8bR031381@colby.verdasys.com>
2008-10-22 20:30     ` Andrew Morton
2008-10-22 21:17       ` James Bottomley
2008-10-23 16:14         ` Marc Bejarano
2008-10-23 16:35           ` James Bottomley
2008-10-27 17:48             ` Marc Bejarano
2008-10-21 22:52 ` [Bug 11800] " bugme-daemon
2008-10-22 19:43 ` bugme-daemon
2008-10-22 20:31 ` bugme-daemon [this message]
2008-10-22 21:17 ` bugme-daemon
2008-10-23 16:15 ` bugme-daemon
2008-10-23 16:35 ` bugme-daemon
2008-10-27 17:48 ` bugme-daemon
     [not found] <bug-11800-11613@https.bugzilla.kernel.org/>
2012-05-14 16:47 ` bugzilla-daemon
2012-05-14 16:47 ` bugzilla-daemon

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=20081022203157.B9AF2108047@picon.linux-foundation.org \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@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.