From: Theodore Ts'o <tytso@mit.edu>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Pavel Machek <pavel@ucw.cz>, Mike Galbraith <efault@gmx.de>,
LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: LKML admins (syzbot emails are not delivered)
Date: Tue, 16 Jan 2018 18:13:13 -0500 [thread overview]
Message-ID: <20180116231313.GL8249@thunk.org> (raw)
In-Reply-To: <CACT4Y+axEZRPxt9+R_2+8Py7BQMrdOowBfsw8XCE==h2+Gc+6A@mail.gmail.com>
On Tue, Jan 16, 2018 at 09:31:26AM +0100, Dmitry Vyukov wrote:
> On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o <tytso@mit.edu> wrote:
> > I just checked a recent report from the Syzbot, and it's not fixed.
> > The raw.log file still uses a Content-Type of
> > Application/Octet-stream. Worse the reproducer C source file has a
> > content type of Application/Octet-stream instead of the much more sane
> > Application/text. <Face palm>
>
>
> I will look into using a different mailing system which allows more
> control over email contents.
> A quick fix for raw.log will be to rename it to raw.log.txt. Not sure
> if text/plain repro.c.txt is better than application/octet-stream
> repro.c...
My personal opinion is that if there is no way to force the content
type except by using magic extensions --- which is super-surprising to
me; that seems like a broken API and a feature request bug should be
filed against the relevant API --- using repro.c.txt would be the best
of bad alternatives. Someone is going to have to exit to a shell to
compile the repro, and renaming the filename isn't a big deal. The
Mail User Agent I use (mutt) allows me to specify the directory to
save the file, and gives me the opportunity to edit the filename,
before I save it. So at least for me, it really isn't a big deal for
you to use repro.c.txt.
Cheers,
- Ted
next prev parent reply other threads:[~2018-01-16 23:13 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 9:09 LKML admins (syzbot emails are not delivered) Dmitry Vyukov
2018-01-04 9:23 ` Greg Kroah-Hartman
2018-01-04 9:56 ` Ozgur
2018-01-04 15:31 ` David Miller
2018-01-04 19:11 ` Ozgur
2018-01-04 11:03 ` Dmitry Vyukov
2018-01-04 11:04 ` Dmitry Vyukov
2018-01-04 11:20 ` Greg Kroah-Hartman
2018-01-04 15:35 ` David Miller
2018-01-15 9:43 ` Dmitry Vyukov
2018-03-01 16:22 ` Dmitry Vyukov
2018-03-08 20:03 ` David Miller
2018-03-12 8:56 ` Dmitry Vyukov
2018-03-12 14:03 ` David Miller
2018-01-04 23:50 ` Theodore Ts'o
2018-01-08 12:01 ` Dmitry Vyukov
2018-01-08 12:11 ` Dmitry Vyukov
2018-01-04 9:25 ` Pavel Machek
2018-01-04 9:38 ` Mike Galbraith
2018-01-04 9:56 ` Pavel Machek
2018-01-04 11:09 ` Dmitry Vyukov
2018-01-04 11:18 ` Pavel Machek
2018-01-15 10:08 ` Dmitry Vyukov
2018-01-15 13:08 ` Pavel Machek
2018-01-15 13:38 ` Dmitry Vyukov
2018-01-15 13:53 ` Pavel Machek
2018-01-04 15:23 ` Eric W. Biederman
2018-01-15 10:54 ` Dmitry Vyukov
2018-01-15 12:54 ` Pavel Machek
2018-01-15 13:02 ` Dmitry Vyukov
2018-01-15 16:16 ` Eric W. Biederman
2018-01-16 18:01 ` Dmitry Vyukov
2018-01-15 16:38 ` Eric W. Biederman
2018-01-16 7:12 ` Theodore Ts'o
2018-01-16 7:51 ` Dmitry Vyukov
2018-01-16 9:52 ` Guenter Roeck
2018-01-16 9:56 ` Dmitry Vyukov
2018-01-16 9:58 ` Guenter Roeck
2018-01-16 7:59 ` Dmitry Vyukov
2018-01-16 11:19 ` Fengguang Wu
2018-01-16 8:31 ` Dmitry Vyukov
2018-01-16 23:13 ` Theodore Ts'o [this message]
2018-01-17 8:06 ` Dmitry Vyukov
2018-01-17 16:53 ` Theodore Ts'o
2018-01-17 17:16 ` Dmitry Vyukov
2018-01-17 22:27 ` Bernd Petrovitsch
2018-01-16 8:34 ` Dmitry Vyukov
2018-01-24 16:04 ` Alan Cox
2018-01-24 17:06 ` Eric W. Biederman
2018-01-24 17:32 ` Greg Kroah-Hartman
2018-01-16 18:20 ` Dmitry Vyukov
2018-01-17 8:13 ` Dmitry Vyukov
2018-01-04 21:38 ` Pavel Machek
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=20180116231313.GL8249@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=efault@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=syzkaller@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox