From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 14328] New: Consistent the size type. New logic to use.
Date: Mon, 5 Oct 2009 21:23:36 GMT [thread overview]
Message-ID: <bug-14328-11311@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=14328
Summary: Consistent the size type. New logic to use.
Product: Documentation
Version: unspecified
Kernel Version: 2.6.30.9
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
AssignedTo: documentation_man-pages-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
ReportedBy: vik-cfgfcfnPGrx6k2ZkT/Rh8A@public.gmane.org
Regression: No
It is possible to do consistent the sizeof(). Just the size type be unsigned.
Next is sample:
unsigned long *p,*p2,length;
p=some_value;
p2=p;
length=sizeof(type_or_lvalue);
p+=length;
if(p<p2)
catch_overrun...
*p=some_value2;
However the error codes is negative so it is hard to accept big size. Are the
race of system calls and kernel subroutines is different?
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2009-10-05 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 21:23 bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
[not found] ` <bug-14328-11311-V0hAGp6uBxO456/isadD/XN4h3HLQggn@public.gmane.org/>
2009-10-06 8:54 ` [Bug 14328] Consistent the size type. New logic to use bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2009-11-01 11:00 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
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=bug-14328-11311@http.bugzilla.kernel.org/ \
--to=bugzilla-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.