All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ashishx88" <ashish.emailaddress@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Inputs to share CVE patch for binutils CVE-2023-25584
Date: Sun, 21 Jan 2024 08:43:16 -0800	[thread overview]
Message-ID: <cSDk.1705855396440281429.AFnV@lists.openembedded.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 961 bytes --]

Hi Members ,

I am trying to submit an CVE patch  CVE-2023-25584 for binutils
*This is my first patch in community so apologies if any basic info is missed*

Can members please help me for

1) Do i need to share only specific CVE patch with community
or
Patch with updates meta/recipes-devtools/binutils/binutils-2.39.inc &  CVE  both files being updated in same patch
(Currently this is what i have created )

2) Is there any known place where i can share that i am looking at this CVE so we save effort duplication

3) Can i share the patch as attachment here or i need to send via " git send-email " only.
Currently i am facing some issue with git send-email at my end

4) I have validated the patch for (langdale) :
# devtool build binutils
# devtool build-image core-image-minimal
# bitbake binutils (after  cleanall )
# bitbake core-image-minimal
Is there any other test i need to do to ensure the sanity ?

Thanks ,
Ashish.

[-- Attachment #2: Type: text/html, Size: 1700 bytes --]

             reply	other threads:[~2024-01-21 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-21 16:43 Ashishx88 [this message]
2024-01-21 20:12 ` [OE-core] Inputs to share CVE patch for binutils CVE-2023-25584 Khem Raj
2024-01-22  8:00   ` Ashishx88
2024-01-22 15:29     ` Ashishx88

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=cSDk.1705855396440281429.AFnV@lists.openembedded.org \
    --to=ashish.emailaddress@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.