From: Jan Engelhardt <jengelh@inai.de>
To: Kay Sievers <kay@vrfy.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <greg@kroah.com>,
Jukka Ollila <jiiksteri@gmail.com>,
linux-kernel@vger.kernel.org, jbeulich@novell.com,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Regression - /proc/kmsg does not (always) block for 1-byte reads
Date: Fri, 10 Aug 2012 14:56:54 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.01.1208101455420.23731@frira.zrqbmnf.qr> (raw)
In-Reply-To: <CAPXgP12vGkh1q4-L3+wYY5XWZURBXOWQCmovARr0cbf+dHinVQ@mail.gmail.com>
On Saturday 2012-07-07 23:19, Kay Sievers wrote:
>On Fri, Jul 6, 2012 at 10:30 PM, Linus Torvalds
><torvalds@linux-foundation.org> wrote:
>> Kay, this needs to be fixed.
>>
>> Suggested fix: just use the 'seq_printf()' interfaces, which do the
>> proper buffering, and allow any size reads of various packetized data.
>
>I'll have a look.
>
>> Of course, I'd also suggest that whoever was the genius who thought it
>> was a good idea to read things ONE F*CKING BYTE AT A TIME with system
>> calls for each byte should be retroactively aborted. Who the f*ck does
>> idiotic things like that? How did they noty die as babies, considering
>> that they were likely too stupid to find a tit to suck on?
>
>Maybe the bs=1 in the dd call stands for bullshit. :)
It seems people need to be taught to use ddrescue, stringently.
Having to calculate appropriate values for bs= and count= when
you just want to transfer bytes is already a crime, not to mention
the problem when you have a prime number of bytes to transfer.
next prev parent reply other threads:[~2012-08-10 12:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 17:45 Bug 44211 - /proc/kmsg does not (always) block for 1-byte reads Jukka Ollila
2012-07-06 17:55 ` Greg KH
2012-07-06 18:46 ` Jukka Ollila
2012-07-08 12:37 ` Kay Sievers
2012-07-08 12:59 ` Alan Cox
2012-07-08 13:06 ` Kay Sievers
2012-07-06 19:38 ` Regression " Alan Cox
2012-07-06 20:30 ` Linus Torvalds
2012-07-07 21:19 ` Kay Sievers
2012-07-08 2:09 ` Kay Sievers
2012-08-10 12:56 ` Jan Engelhardt [this message]
2012-07-06 22:05 ` Jukka Ollila
2012-07-06 22:09 ` Linus Torvalds
2012-07-08 0:33 ` Kay Sievers
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=alpine.LNX.2.01.1208101455420.23731@frira.zrqbmnf.qr \
--to=jengelh@inai.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=jbeulich@novell.com \
--cc=jiiksteri@gmail.com \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.