All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: dvyukov@google.com, linux-kernel-mentees@lists.linux.dev,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	syzbot@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot ci] Re: net: Revert tx queue length on partial failure in dev_qdisc_change_tx_queue_len()
Date: Thu, 7 Aug 2025 08:26:59 -0700	[thread overview]
Message-ID: <20250807082659.5557e42b@kernel.org> (raw)
In-Reply-To: <CANp29Y5mZJJgn5LYDiLx11bH__NXZ32ut6VUTsEyXwqrOhksTw@mail.gmail.com>

On Thu, 7 Aug 2025 17:09:24 +0200 Aleksandr Nogikh wrote:
> > One more thing, would it be possible to add / correct the DKIM on these
> > messages? Looks like when our bots load the syzbot ci emails from lore
> > the DKIM verification fails. I see a X-Google-DKIM-Signature: header,
> > but no real DKIM-Signature:  
> 
> Thanks for letting us know!
> Do these bots also face DKIM verification issues with regular syzbot
> emails? We send them absolutely the same way, so the problem must
> affect all reports.

I haven't checked, TBH, we don't have any automation for normal
reports :( For the CI reports I was trying to hook them up to
some actions, kick the patch out of our test branch unless human
confirms that the report is a false positive.

> We use the GAE Mail API, and its documentation[1] says that it signs
> emails with DKIM only if a custom domain is configured. Since we send
> from the default GAE domain, this would explain the verification
> failures.
> 
> We'll explore the ways to fix this.
> 
> [1] https://cloud.google.com/appengine/docs/standard/services/mail?tab=go#authentication_with_domainkeys_identified_mail_dkim

      reply	other threads:[~2025-08-07 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22 16:40 [syzbot ci] Re: net: Revert tx queue length on partial failure in dev_qdisc_change_tx_queue_len() syzbot ci
2025-07-22 17:07 ` Jakub Kicinski
2025-07-23 16:25   ` Aleksandr Nogikh
2025-07-23 16:47     ` Jakub Kicinski
2025-08-07 13:41       ` Jakub Kicinski
2025-08-07 15:09         ` Aleksandr Nogikh
2025-08-07 15:26           ` Jakub Kicinski [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=20250807082659.5557e42b@kernel.org \
    --to=kuba@kernel.org \
    --cc=dvyukov@google.com \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nogikh@google.com \
    --cc=syzbot@lists.linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.