login
Login
/
Register
Search
Forums
News
Blogs
Features
Site
Home
»
Mailing list archives
»
linux-kernel
»
2007
»
November
»
11
Re: [PATCH] time: fix sysfs_show_{available,current}_clocksources() buffer overflow problem
view
thread
!MAILaRCHIVE_VOTE_RePLACE
Previous message: [
thread
] [
date
] [
author
]
Next message: [thread] [
date
] [
author
]
[view in full thread]
From:
WANG Cong <xiyou.wangcong@...>
To: Miao Xie <miaox@...>
Cc: WANG Cong <xiyou.wangcong@...>, <tglx@...>, <linux-kernel@...>
Subject:
Re: [PATCH] time: fix sysfs_show_{available,current}_clocksources() buffer overflow problem
Date: Sunday, November 11, 2007 - 12:09 am
On Sun, Nov 11, 2007 at 11:29:59AM +0800, Miao Xie wrote:
quoted text
>on 2007-11-8 20:11 WANG Cong wrote: >>On Thu, Nov 08, 2007 at 07:47:41PM +0800, WANG Cong wrote: >>>Yes, snprintf is safer than sprintf. But here, the 'count' will be >>>mis-pointed when snprintf returns no less than PAGE_SIZE (what you called >>>overflow). So you may also need: >>> >>> if (unlikely(count >= PAGE_SIZE)) >>> count = PAGE_SIZE - 1; >>> >>>Just a simple guess. ;) >> >>Or try scnprintf. ;) > >We have discussed this problem. We think that it is better to return the >return >value of kernel directly because this is the specification of the sysfs. > > (Version:2.6.24-rc2,File:Documentation/filesystems/sysfs.txt:198-201): > 198 - show() methods should return the number of bytes printed into the > 199 buffer. This is the return value of snprintf(). > 200 > 201 - show() should always use snprintf(). > >And the function which calls the show() methods uses BUG_ON() to check the >return value. If the return value is too big,it means something wrong. > >If we use scnprintf, we may not know whether the resulting string is >truncated >or not. Maybe A big bug is ignored. >
Well, i know little about sysfs. So it was just a hint. Anyway, thanks for your input! -
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Previous message: [
thread
] [
date
] [
author
]
Next message: [thread] [
date
] [
author
]
Messages in current thread:
[PATCH] time: fix sysfs_show_{available,current}_clocksource...
, Miao Xie
, (Thu Nov 8, 6:53 am)
Re: [PATCH] time: fix sysfs_show_{available,current}_clockso...
, WANG Cong
, (Thu Nov 8, 7:47 am)
Re: [PATCH] time: fix sysfs_show_{available,current}_clockso...
, WANG Cong
, (Thu Nov 8, 8:11 am)
Re: [PATCH] time: fix sysfs_show_{available,current}_clockso...
, Miao Xie
, (Sat Nov 10, 11:29 pm)
Re: [PATCH] time: fix sysfs_show_{available,current}_clockso...
, WANG Cong
, (Sun Nov 11, 12:09 am)
Navigation
Create content
Mailing list archives
Recent posts
Popular discussions
linux-kernel
:
Tarkan Erimer
Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
Greg KH
[GIT PATCH] driver core patches against 2.6.24
David Newall
Re: Slow DOWN, please!!!
Peter Zijlstra
[PATCH 00/23] per device dirty throttling -v8
linux-netdev
:
Jarek Poplawski
[PATCH] pkt_sched: Destroy gen estimators under rtnl_lock().
Gerrit Renker
[PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side)
David Miller
[GIT]: Networking
Natalie Protasevich
[BUG] New Kernel Bugs
openbsd-misc
:
git
:
Colocation donated by:
Who's online
There are currently
1 user
and
645 guests
online.
Online users
roundthejollyro
Syndicate