public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ollie Lho <ollie@sis.com.tw>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Fabrizio Pollastri <pollastri@iriti.cnr.it>, mtd@infradead.org
Subject: sszie_t and loff_t V.S u_int32_t (Was Re: Problems with nftl_format)
Date: Tue, 10 Apr 2001 12:21:59 +0800	[thread overview]
Message-ID: <3AD28A67.9D61C5AA@sis.com.tw> (raw)
In-Reply-To: 18147.986809264@redhat.com

David Woodhouse wrote:
> 
> pollastri@iriti.cnr.it said:
> > MEMWRITEOOB at 14200: Invalid argument
> 
> OK, I probably broke it when I changed the structures slightly to make
> sparc64 happy. Can you confirm or deny my suspicion that it broke on the
> 17th of March?
> 
> Does it start to work again if you recompile nftl_format against the new
> headers?
> 

David,
	I think the problem should be that you have changed the definition
of struct mtd_oob_buf. In older header file you have:

struct mtd_oob_buf {
        loff_t start;
        ssize_t length;  
        unsigned char *ptr;
};

and in newer header file:

struct mtd_oob_buf {
        loff_t start;
        ssize_t length;  
        unsigned char *ptr;
};

But you still use loff_t and ssize_t in mtd_ioctl in mtdchar.c

		ret = (mtd->write_oob)(mtd, buf.start, buf.length, &retlen, 			
databuf);

		if (copy_to_user((void *)arg + sizeof(loff_t), &retlen, 			
sizeof(ssize_t)))
			ret = -EFAULT;

Dose this cause any problem ??

Ollie


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

      reply	other threads:[~2001-04-10  4:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-09  9:24 Problems with nftl_format Fabrizio Pollastri
2001-04-09  9:41 ` David Woodhouse
2001-04-10  4:21   ` Ollie Lho [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=3AD28A67.9D61C5AA@sis.com.tw \
    --to=ollie@sis.com.tw \
    --cc=dwmw2@infradead.org \
    --cc=mtd@infradead.org \
    --cc=pollastri@iriti.cnr.it \
    /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