From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Dave Young <dyoung@redhat.com>, Michal Hocko <mhocko@kernel.org>
Cc: linux-pci@vger.kernel.org, "Jörg Rödel" <joro@8bytes.org>,
"x86@kernel.org" <x86@kernel.org>,
kexec@lists.infradead.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
iommu@lists.linux-foundation.org, kasong@redhat.com,
lijiang@redhat.com, "Donald Buczek" <buczek@molgen.mpg.de>
Subject: Messages to kexec@ get moderated (was: Crash kernel with 256 MB reserved memory runs into OOM condition)
Date: Thu, 15 Aug 2019 19:00:03 +0200 [thread overview]
Message-ID: <9f125599-33a9-4dfd-be05-04335a36c52e@molgen.mpg.de> (raw)
In-Reply-To: <20190813024600.GA2944@dhcp-128-65.nay.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 958 bytes --]
Dear Dave,
On 13.08.19 04:46, Dave Young wrote:
> On 08/13/19 at 10:43am, Dave Young wrote:
[…]
> The question is to Paul, also it would be always good to cc kexec mail
> list for kexec and kdump issues.
kexec@ was CCed in my original mail, but my messages got moderated. It’d
great if you checked that with the list administrators.
> Your mail to 'kexec' with the subject
>
> Crash kernel with 256 MB reserved memory runs into OOM condition
>
> Is being held until the list moderator can review it for approval.
>
> The reason it is being held:
>
> Message has a suspicious header
>
> Either the message will get posted to the list, or you will receive
> notification of the moderator's decision. If you would like to cancel
> this posting, please visit the following URL:
>
> http://lists.infradead.org/mailman/confirm/kexec/a23ab6162ef34d099af5dd86c46113def5152bb1
Kind regards,
Paul
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]
prev parent reply other threads:[~2019-08-15 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d65e4a42-1962-78c6-1b5a-65cb70529d62@molgen.mpg.de>
2019-08-12 9:50 ` Crash kernel with 256 MB reserved memory runs into OOM condition Michal Hocko
2019-08-12 9:59 ` Paul Menzel
2019-08-13 2:43 ` Dave Young
2019-08-13 2:46 ` Dave Young
2019-08-13 2:54 ` Dave Young
2019-09-04 10:10 ` Paul Menzel
2019-08-15 17:00 ` Paul Menzel [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=9f125599-33a9-4dfd-be05-04335a36c52e@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=buczek@molgen.mpg.de \
--cc=dyoung@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kasong@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=lijiang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).