Skip to contentSkip to conversation

New: Consistent the size type. New logic to use.

Bug 14328 bugzilla-daemon-590EEB7GvNiWaY/[email protected] 1 participant 3 messages Oct 5, 2009 – Nov 1, 2009 1 message not in the archive Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore
#0 lore 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/[email protected]
ReportedBy: vik-cfgfcfnPGrx6k2ZkT/[email protected]
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?

Signature · 7 lines
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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): bug-14328-11311-V0hAGp6uBxO456/isadD/[email protected]/

#2 lore raw

[Bug 14328] Consistent the size type. New logic to use.

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

Victor Mineev <vik-cfgfcfnPGrx6k2ZkT/[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement

--- Comment #1 from Victor Mineev <vik-cfgfcfnPGrx6k2ZkT/[email protected]> 2009-10-06 08:54:14 --- Lazy algorithm is the right thing to do. Do user space read a lot better. Let
protect high half of memory region as read/write disabled. So data begin can go
to user space fast soon. And lazy detect of negative size value become true. Is
the kernel do read syncronicly? It is so fantastic to test where is a kvm guest
do the last access.

Signature · 7 lines
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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw

[Bug 14328] Consistent the size type. New logic to use.

In reply to a message not in the archive

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

Alexey Dobriyan <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |[email protected]
         AssignedTo|documentation_man-pages@ker |[email protected]
                   |nel-bugs.osdl.org           |

--- Comment #2 from Alexey Dobriyan <[email protected]> 2009-11-01 11:00:19 --- It's impossible to understand what do you want.

Write me a letter in Russian.
Напиши мне письмо по-русски.

Signature · 6 lines
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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html