linux-kernel - Re: [PATCH v2 2/3] io_uring: minor clean up in trace events definition

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210616094321.671b82dc@gandalf.local.home>
Date:   Wed, 16 Jun 2021 09:43:21 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Olivier Langlois <olivier@...llion01.com>
Cc:     Jens Axboe <axboe@...nel.dk>,
        Pavel Begunkov <asml.silence@...il.com>,
        Ingo Molnar <mingo@...hat.com>, io-uring@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/3] io_uring: minor clean up in trace events
 definition

On Wed, 16 Jun 2021 09:33:18 -0400
Olivier Langlois <olivier@...llion01.com> wrote:

> I do not get any errors but I have noticed too that my emails weren't
> accepted by the lists.
> 
> They will accept replies in already existing threads but they won't let
> me create new ones. ie: accepting my patches.

How are you sending your patches? The patches that were rejected, did not
have the "Message-ID:" tag in the header. If you look at my email (and
yours that I'm replying to now) you'll see something like this:

 Message-ID: <f3cf3dc047dcee400423f526c1fe31510c5bcf61.camel@...llion01.com>

(that's from the email I'm replying to).

All emails are suppose to have this tag. This is what is used to map
replies in a way that your email client can see what email is replying to
which email. Again, from your email:

 In-Reply-To: <def5421f-a3ae-12fd-87a2-6e584f753127@...nel.dk>

That's because the email you replied to had:

 Message-ID: <def5421f-a3ae-12fd-87a2-6e584f753127@...nel.dk>

This is also used for mail archives, as message ids are used to
differentiate emails from each other. But if the Message-ID is missing, the
archives have no idea to map it.

I'm guessing that the mailing lists also flag any email that is missing a
Message-ID as spam.

Thus, you should find out what is wrong with your client software that is
sending out the patches, and see why it's not including the Message-ID.

-- Steve