Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751428AbeAPSVM (ORCPT + 1 other); Tue, 16 Jan 2018 13:21:12 -0500 Received: from mail-pl0-f47.google.com ([209.85.160.47]:38072 "EHLO mail-pl0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750750AbeAPSVL (ORCPT ); Tue, 16 Jan 2018 13:21:11 -0500 X-Google-Smtp-Source: ACJfBotyfVOys01Vs9O/N1aZi6pG5m7j+WePu0zlhJT1BT5dbCoqXakNW8flof41copoAJ5BhcdUpYP3854r/pa5/W4= MIME-Version: 1.0 In-Reply-To: <87efmrt6ul.fsf@xmission.com> References: <20180104092552.GA991@amd> <1515058705.7875.25.camel@gmx.de> <20180104095628.GA4407@atrey.karlin.mff.cuni.cz> <87inchsl4h.fsf@xmission.com> <87efmrt6ul.fsf@xmission.com> From: Dmitry Vyukov Date: Tue, 16 Jan 2018 19:20:49 +0100 Message-ID: Subject: Re: LKML admins (syzbot emails are not delivered) To: "Eric W. Biederman" Cc: Pavel Machek , Mike Galbraith , LKML , Greg Kroah-Hartman , Andrew Morton , Linus Torvalds , syzkaller Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Mon, Jan 15, 2018 at 5:38 PM, Eric W. Biederman wrote: > When I made the complaint it came to me and to messages on lkml as > .log. With Content-Type: Application/Octent-stream. Where was that? If I am not mistaken you actually didn't. I triple-checked my inbox and searched internet. The only references to Content-Type from you I can find are in this thread. And the are "Like Content-type" and "Not content-type in the emails". I simply was not aware of the problem, and I did not understand these comment because they don't explain the problem. The only discussion that happened around Content-Type is this: https://groups.google.com/d/msg/syzkaller/2nVn_XkVhEE/7DjzSA2jCgAJ This is proposal to give files .syz extension, which does not look right to me and it a different topic anyway. > That is a bloody mess that wastes peoples time. If it is fixed good, > it certainly was not fixed at that point. > > But it is much more than any single issue. You get defensive when > people critisize syzbot. Instead of recognizing it's failings.