From: Andrew Morton <akpm@osdl.org>
To: Joe <joecool1029@gmail.com>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: Device Node Issues with recent mm's and udev
Date: Wed, 27 Apr 2005 17:01:06 -0700 [thread overview]
Message-ID: <20050427170106.782ea4c3.akpm@osdl.org> (raw)
In-Reply-To: <d4757e6005042716523af66bae@mail.gmail.com>
Joe <joecool1029@gmail.com> wrote:
>
> This issue started to appear in around the 2.6.11-mm series.. it
> continues even now with 2.6.12-rc2-mm3.
>
> Attempting to copy an image to a device with a tool like dd, results
> in the device node being overwritten with the data, but the data is
> never sent to the destination drive for instance.
>
> To try to put it more plainly, I have a firmware image I am copying to
> an ipod. Normally the image sends with no issues and the ipod has the
> new firmware.
>
> With the recent mm's it treats the device node as a file and ls -l
> will show the size of the image as the size of the device node.
>
> Even things like fdisk are useless. I am not sure whether this is
> some sort of a udev crash or a problem with usb-storage. Nevertheless
> it is a problem, and it continues to happen.
>
> The last non-affected mm i can think of is 2.6.11-rc4-mm1.. though I'm
> fairly sure rc5 is good too.
Greg stuff.
Is the device node in /dev actually a block-special device, or is is coming
up as a regular file or something?
We might have fixed this. Please retest next -mm, which right now is
looking to be ~30 hours away.
next prev parent reply other threads:[~2005-04-28 0:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 23:52 Joe
2005-04-28 0:01 ` Andrew Morton [this message]
2005-04-28 0:15 ` Joe
2005-04-28 6:40 ` Denis Vlasenko
2005-04-28 19:38 ` Joe
2005-04-28 4:14 ` Greg KH
2005-04-28 4:57 ` Joe
2005-04-28 5:03 ` Greg KH
2005-04-28 5:20 ` Joe
2005-04-28 5:23 ` Greg KH
2005-04-28 5:32 ` Joe
2005-04-28 6:05 ` Greg KH
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=20050427170106.782ea4c3.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=joecool1029@gmail.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
Powered by JetHome