All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org,
	"Philippe Mathieu-Daudé" <philmd@mailo.com>
Subject: Re: [RFC PATCH v3] AGENTS.md: basic bare minimal guide
Date: Thu, 3 Sep 2026 14:34:54 +0100	[thread overview]
Message-ID: <apl3ftMWA44nHexR@redhat.com> (raw)
In-Reply-To: <CAFEAcA_TaGW+7jvtp8OXjvGeJMce75MzZrimCWyaHrfa+ttx7w@mail.gmail.com>

On Thu, Sep 03, 2026 at 02:24:39PM +0100, Peter Maydell wrote:
> On Thu, 3 Sept 2026 at 13:25, Alex Bennée <alex.bennee@linaro.org> wrote:
> >
> > Currently people may be inadvertently not following our documented
> > process for code submissions because people often don't read the docs.
> > However AI Agents do tend to try and follow instructions so lets help
> > them out.
> >
> > Suggested-by: Peter Maydell <peter.maydell@linaro.org>
> > Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> 
> > diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md
> > new file mode 120000
> > index 00000000000..be77ac83a18
> > --- /dev/null
> > +++ b/.claude/CLAUDE.md
> > @@ -0,0 +1 @@
> > +../AGENTS.md
> > \ No newline at end of file
> 
> Missing newline, as git notes.

IIUC, that's just a result of how git represents symlinks

> 
> > +## Security Policy (see `docs/system/security.rst`)
> > +
> > +You MUST NOT report potential security vulnerabilities to the public
> > +GitLab issue tracker as a normal issue. They should be reported as a
> > +GitLab "confidential" work item, as described at
> > +https://www.qemu.org/contribute/security-process/
> > +
> > +**Crucial for AI Triage**: Not every crash, assertion failure, or
> > +buffer overrun is a security vulnerability. Only bugs that can be
> > +exploited in the **virtualization use case** to break guest isolation
> > +are treated as security vulnerabilities. In brief these are:
> > +- **Hardware Accelerators**: e.g. KVM and Xen, TCG is explicitly excluded.
> 
> "Xen. TCG", not a comma. Otherwise it's unclear whether you're
> including or excluding KVM and Xen.

If that change is made, then add

 Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
 

With regards,
Daniel
-- 
|: https://berrange.com       ~~        https://hachyderm.io/@berrange :|
|: https://libvirt.org          ~~          https://entangle-photo.org :|
|: https://pixelfed.art/berrange   ~~    https://fstop138.berrange.com :|



  reply	other threads:[~2026-09-03 13:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 12:25 [RFC PATCH v3] AGENTS.md: basic bare minimal guide Alex Bennée
2026-09-03 13:24 ` Peter Maydell
2026-09-03 13:34   ` Daniel P. Berrangé [this message]
2026-09-03 15:17     ` Philippe Mathieu-Daudé

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=apl3ftMWA44nHexR@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@mailo.com \
    --cc=qemu-devel@nongnu.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 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.