From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: New warnings on NTFS code
Date: Wed, 28 Apr 2004 09:38:21 +0100 [thread overview]
Message-ID: <1083141501.2035.25.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <Pine.GSO.4.44.0404281106040.24906-100000@math.ut.ee>
On Wed, 2004-04-28 at 09:13, Meelis Roos wrote:
> This is 2.6.6-rc3 on sparc64. It has recently got some new warnings in
> NTFS (there was a warning before but now there are more):
>
> fs/ntfs/super.c: In function `parse_ntfs_boot_sector':
> fs/ntfs/super.c:638: warning: long long unsigned int format, s64 arg (arg 4)
Oops. A missing cast in a printf(). Now fixed in my tree.
> fs/ntfs/super.c: In function `ntfs_fill_super':
> fs/ntfs/super.c:1523: warning: cast to pointer from integer of different size
> fs/ntfs/super.c:1529: warning: cast to pointer from integer of different size
> fs/ntfs/super.c:1634: warning: cast to pointer from integer of different size
>
> The 3 new warnings are because of this definition:
>
> #define OGIN ((struct inode*)le32_to_cpu(0x4e49474f)) /* OGIN */
>
> This seems suspicious - hardcoded pointer?
It is a pointer poison. Now fixed in my tree.
I will submit the fixes with the next NTFS release which should be in a
few weeks. None of the above indicate anything is broken, so there is
no hurry...
Thanks for the report!
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ &
http://www-stu.christs.cam.ac.uk/~aia21/
prev parent reply other threads:[~2004-04-28 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 8:13 Meelis Roos
2004-04-28 8:38 ` Anton Altaparmakov [this message]
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=1083141501.2035.25.camel@imp.csi.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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
all inboxes | Powered by JetHome®