From: Bruno Meneguele <bmeneg@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Petr Mladek <pmladek@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
David Laight <David.Laight@aculab.com>
Subject: Re: [PATCH] Revert "kernel/printk: add kmsg SEEK_CUR handling"
Date: Mon, 22 Jun 2020 14:37:41 -0300 [thread overview]
Message-ID: <20200622173741.GA8956@glitch> (raw)
In-Reply-To: <CAHk-=wg6vtnyxW6DR6_pTmMowjd9SuULu4C0DJBXCzJz8XgyXg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
On Mon, Jun 22, 2020 at 10:32:51AM -0700, Linus Torvalds wrote:
> On Mon, Jun 22, 2020 at 10:10 AM Bruno Meneguele <bmeneg@redhat.com> wrote:
> >
> > Although both options are pretty fine by me too, I "fear" (not really)
> > we can end up stacking special behavior interfaces, forcing userspace to
> > keep a "table of special case files". Personally, I prefer to return
> > something _valid_ to userspace rather than _fail_ with special meaning.
>
> Well, what's even worse if user space has to handle two different
> things just because behavior changed in different kernels..
>
> So at some point "odd behavior" is much better than "odd behavior in
> two different ways"..
Really well pointed!
Ok, +1 for doc-only patch it is :).
--
bmeneg
PGP Key: http://bmeneg.com/pubkey.txt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-22 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 3:02 [PATCH] Revert "kernel/printk: add kmsg SEEK_CUR handling" Jason A. Donenfeld
2020-06-22 3:50 ` Linus Torvalds
2020-06-22 13:37 ` Bruno Meneguele
2020-06-22 16:42 ` Linus Torvalds
2020-06-22 17:10 ` Bruno Meneguele
2020-06-22 17:32 ` Linus Torvalds
2020-06-22 17:37 ` Bruno Meneguele [this message]
2020-07-11 22:28 ` Jason A. Donenfeld
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=20200622173741.GA8956@glitch \
--to=bmeneg@redhat.com \
--cc=David.Laight@aculab.com \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--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.