From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev problem (and fix) for /dev/mtdblock*
Date: Mon, 23 Mar 2009 22:23:00 +0000 [thread overview]
Message-ID: <200903231523.00438.david-b@pacbell.net> (raw)
In-Reply-To: <ac3eb2510903181845r62f3ed39sd5c8e4dd0ac39c7a@mail.gmail.com>
On Monday 23 March 2009, Kay Sievers wrote:
> On Mon, Mar 23, 2009 at 21:39, David Brownell <david-b@pacbell.net> wrote:
> > On Monday 23 March 2009, Kay Sievers wrote:
> >> > OTP data in lot of the NAND chips I have here exceeds the sysfs 4KB
> >> > binary file limit; 20KB commonly, 128KB for OneNand.
> >>
> >> There is no such limit for binary sysfs files. We have many large file
> >> there, which map such sizes.
> >
> > Odd, just the other day I created one with actual size of 8KB.
> > But "ls -l" showed 4K.
>
> There are larger files:
Could be. But still ... I set the size of the attribute to 8K,
but "ls" reported only 4K.
> > Something seems odd with binary sysfs files in general. I've
> > observed something zapping size down to zero after userspace
> > did some oddball reads ... of the "past EOF" variety, ISTR.
>
> Hmm, never seen such a thing, but the logic is implemented per-file,
> so it might be something that should be fixed in the driver that
> created the file.
All those drivers do is respond to read/write calls, and set
the size statically.
I've seen both those failures in multiple drivers, FWIW.
- Dave
next prev parent reply other threads:[~2009-03-23 22:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 1:45 udev problem (and fix) for /dev/mtdblock* Kay Sievers
2009-03-19 10:08 ` Scott James Remnant
2009-03-20 18:46 ` David Brownell
2009-03-22 15:39 ` Kay Sievers
2009-03-23 18:49 ` David Brownell
2009-03-23 20:17 ` Kay Sievers
2009-03-24 21:14 ` David Brownell
2009-03-23 20:39 ` David Brownell
2009-03-23 21:21 ` Kay Sievers
2009-03-23 22:23 ` David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-18 19:44 Fwd: " David Brownell
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=200903231523.00438.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).