From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: He Zhe <zhe.he@windriver.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
pmladek@suse.com, sergey.senozhatsky@gmail.com,
rostedt@goodmis.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: Fix unnecessary returning broken pipe error from devkmsg_read
Date: Tue, 24 Sep 2019 10:10:18 +0900 [thread overview]
Message-ID: <20190924011018.GA3864@jagdpanzerIV> (raw)
In-Reply-To: <027b2f0d-b7dc-4e76-22a7-ce80c9a0aade@windriver.com>
On (09/23/19 18:45), He Zhe wrote:
> I think it is NOT necessary to inform user-space, when it just wants to read
> from the beginning of the buffer, that the buffer has changed since the time
> point when it issues the action of reading.
The point here is not to notify user space that the logbuf has changed,
but to notify user space that unseen messages are gone, we lost them,
user space will never read them.
-ss
prev parent reply other threads:[~2019-09-24 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 13:31 [PATCH] printk: Fix unnecessary returning broken pipe error from devkmsg_read zhe.he
2019-09-23 10:05 ` Sergey Senozhatsky
2019-09-23 10:45 ` He Zhe
2019-09-23 11:39 ` Petr Mladek
2019-09-23 14:11 ` He Zhe
2019-09-23 19:58 ` John Ogness
2019-09-24 1:10 ` Sergey Senozhatsky [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=20190924011018.GA3864@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=zhe.he@windriver.com \
/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