mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Jones <davej@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Wu Fengguang <fengguang.wu@intel.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] x86info fails on 2.6.34 ?
Date: Mon, 05 Apr 2010 23:04:08 +0200	[thread overview]
Message-ID: <1270501448.9013.23.camel@edumazet-laptop> (raw)
In-Reply-To: <1270499041.9013.15.camel@edumazet-laptop>

Le lundi 05 avril 2010 à 22:24 +0200, Eric Dumazet a écrit :
> Hi Dave
> 
> I just noticed x86info was not working anymore on latest kernel
> 
> x86info v1.24.  Dave Jones 2001-2009
> Feedback to <davej@redhat.com>.
> 
> type seek: Value too large for defined data type
> 
> 
> Offending syscall is an lseek(fd, -1, SEEK_CUR) on /dev/mem file
> 
> 
> 
> open("/dev/mem", O_RDONLY)              = 3
> ...
> lseek(3, 1023092, SEEK_SET)             = 1023092
> read(3, "PCMP\4\3\4\266HP      PROLIANT    \0\0\0\0\0"..., 44) = 44
> read(3, "\0"..., 1)                     = 1
> lseek(3, -1, SEEK_CUR)                  = -1 EOVERFLOW (Value too large
> for defined data type)
> 
> It seems -1 is taken as an unsigned quantity ?
> 

Andrew, commit dcefafb6ac90ece8d68a6c203105f3d313e52da4 seems to be the
problem. 

It breaks rewinds (negative offsets to lseek (... SEEK_CUR))


commit dcefafb6ac90ece8d68a6c203105f3d313e52da4
Author: Wu Fengguang <fengguang.wu@intel.com>
Date:   Wed Mar 10 15:21:51 2010 -0800

    /dev/mem: dont allow seek to last page
    
    So as to return a uniform error -EOVERFLOW instead of a random one:
    
    # kmem-seek 0xfffffffffffffff0
    seek /dev/kmem: Device or resource busy
    # kmem-seek 0xfffffffffffffff1
    seek /dev/kmem: Block device required
    
    Suggested by OGAWA Hirofumi.
    
    Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
    Reviewed-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
    Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>




  reply	other threads:[~2010-04-05 21:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 20:24 Eric Dumazet
2010-04-05 21:04 ` Eric Dumazet [this message]
2010-04-05 21:19   ` [PATCH] /dev/mem: Allow rewinding Eric Dumazet
2010-04-06  5:15     ` Wu Fengguang
2010-04-06  5:30     ` Américo Wang
2010-04-06  5:43       ` Wu Fengguang
2010-04-06  6:24         ` Américo Wang
2010-04-06  6:21       ` Eric Dumazet

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=1270501448.9013.23.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.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 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®