| Message ID | 20180809181103.15437-1-matwey@sai.msu.ru (mailing list archive) |
|---|---|
| Headers | show |
| Series | media: usb: pwc: Don't use coherent DMA buffers for ISO transfer | expand |
Matwey,
your DKIM signature is garbage, and it causes your emails to be
marked as spam when they go through a mailing list.
The reason is this:
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20161025;
h=sender:from:to:cc:subject:date:message-id;
where the problem is that the "sender" field is included in the DKIM
hash calculation.
That is completely incorrect, since a mailing list will - by
definition - change the sender to the list, not the original sender.
This is not a mailing list bug. This is a bug in your DKIM setup on
the sending side.
I'm leaving everybody cc'd., because this problem is starting to be
annoyingly common. We had two people with chromium.org addresses with
the same misconfiguration, and I want people to be aware of this.
I get too much email, and too much spam, and so when people have
misc-onfigured email sending that causes problems for spam systems, it
needs to get fixed.
Your situation *may* be the same as the Chromium guys. Quoting Doug:
"Looks like it's all fixed. Both Kees and I setup our chromium.org
accounts a long time ago. IIRC during that time the suggested way to
do things was that you'd use your @google.com SMTP settings even when
you were sending as your @chroumium.org account. These days it
doesn't appear that there's even any UI in gmail to configure things
that way, so presumably nobody else will be stuck in the same hole
that Kees and I were in"
and he may have been wrong about that "presumably nobody else will be
stuck in the same hole" guess.
So you might want to check what the SMTP settings are for your setup.
Linus
Hi Linus, Thanks for pointing it out, I'll try to do my best to avoid this in future. As I see now, in my case, the 'sender' in DKIM is triggered when using GMail with alien domain in "Send From:". I would not say that it is configuration "bug" (at least I can imagine why do they do that), but it definitely must be avoided for maillists. It is also interesting that if I use alien "From" email address with google-apps (g suite) domain, then GMail generated two DKIM-Signature headers, both for gmail.com and for the google-apps domain. 2018-08-09 22:31 GMT+03:00 Linus Torvalds <torvalds@linux-foundation.org>: > Matwey, > your DKIM signature is garbage, and it causes your emails to be > marked as spam when they go through a mailing list. > > The reason is this: > > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > d=gmail.com; s=20161025; > h=sender:from:to:cc:subject:date:message-id; > > where the problem is that the "sender" field is included in the DKIM > hash calculation. > > That is completely incorrect, since a mailing list will - by > definition - change the sender to the list, not the original sender. > > This is not a mailing list bug. This is a bug in your DKIM setup on > the sending side. > > I'm leaving everybody cc'd., because this problem is starting to be > annoyingly common. We had two people with chromium.org addresses with > the same misconfiguration, and I want people to be aware of this. > > I get too much email, and too much spam, and so when people have > misc-onfigured email sending that causes problems for spam systems, it > needs to get fixed. > > Your situation *may* be the same as the Chromium guys. Quoting Doug: > > "Looks like it's all fixed. Both Kees and I setup our chromium.org > accounts a long time ago. IIRC during that time the suggested way to > do things was that you'd use your @google.com SMTP settings even when > you were sending as your @chroumium.org account. These days it > doesn't appear that there's even any UI in gmail to configure things > that way, so presumably nobody else will be stuck in the same hole > that Kees and I were in" > > and he may have been wrong about that "presumably nobody else will be > stuck in the same hole" guess. > > So you might want to check what the SMTP settings are for your setup. > > Linus
From: "Matwey V. Kornilov" <matwey.kornilov@gmail.com> DMA cocherency slows the transfer down on systems without hardware coherent DMA. In order to demontrate this we introduce performance measurement facilities in patch 1 and fix the performance issue in patch 2 in order to obtain 4 times speedup. Changes since v3: * fix scripts/checkpatch.pl errors * use __string to store name in trace events Changes since v2: * use dma_sync_single_for_cpu() to achive better performance * remeasured performance Changes since v1: * trace_pwc_handler_exit() call moved to proper place * detailed description added for commit 1 * additional output added to trace to track separate frames Matwey V. Kornilov (2): media: usb: pwc: Introduce TRACE_EVENTs for pwc_isoc_handler() media: usb: pwc: Don't use coherent DMA buffers for ISO transfer drivers/media/usb/pwc/pwc-if.c | 63 ++++++++++++++++++++++++++++++++-------- include/trace/events/pwc.h | 65 ++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 116 insertions(+), 12 deletions(-) create mode 100644 include/trace/events/pwc.h