public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Marcel Runte <marcel.runte@web.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Kernel oops after compile error
Date: Thu, 31 Jul 2008 09:43:12 -0400	[thread overview]
Message-ID: <1217511792.20239.42.camel@think.oraclecorp.com> (raw)
In-Reply-To: <1905261913@web.de>

On Thu, 2008-07-31 at 00:44 +0200, Marcel Runte wrote:
> Hello,
>=20
> I fiddled around with btrfs this evening and need some further insigh=
t into this error.
>=20
> During compilation this error occurs:
>=20
> /home/runtema/btrfs_build/kernel-9da425337329/file.c: In Funktion =C2=
=BBbtrfs_file_write=C2=AB:
> /home/runtema/btrfs_build/kernel-9da425337329/file.c:851: Warnung: =C3=
=9Cbergabe des Arguments 1 von =C2=BBremove_suid=C2=AB von inkompatible=
m Zeigertyp
>=20

Btrfs should compile without warnings, in general any warning is a bug.
The incompatible pointer argument warnings are almost always bugs.  In
this case, the ubuntu kernel has a patch that changes the arguments of
the remove_suid call, and btrfs needs to call it differently.

But, recent versions of Btrfs should be doing the right thing.  Which
version are you running?

-chris


--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-07-31 13:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 22:44 Kernel oops after compile error Marcel Runte
2008-07-31  1:11 ` Yan Zheng
2008-07-31 13:43 ` Chris Mason [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-31 18:53 Marcel Runte
2008-08-01  3:01 ` Yan Zheng

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=1217511792.20239.42.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marcel.runte@web.de \
    /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