From: <nobuhiro1.iwamatsu@toshiba.co.jp> To: <cip-dev@lists.cip-project.org> Cc: <pavel@denx.de>, <jan.kiszka@siemens.com>, <Chris.Paterson2@renesas.com>, <uli@fpond.eu>, <masami.ichikawa@cybertrust.co.jp> Subject: [ANNOUNCE] Release v4.4.285-cip63 Date: Mon, 4 Oct 2021 08:15:20 +0000 [thread overview] Message-ID: <TYAPR01MB6252C6286EDCA87D7DB8B10892AE9@TYAPR01MB6252.jpnprd01.prod.outlook.com> (raw) Hi all, CIP kernel team has released Linux kernel v4.4.285-cip63. The linux-4.4.y-cip tree has been updated from v4.4.283 to v4.4.285. The release information is shown below. v4.4.285-cip63: repository: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git branch: linux-4.4.y-cip commit hash: 18016d4e60e0ab15de4683f6caf64b6289612ac6 Fixed CVEs: CVE-2020-16119: dccp: don't duplicate ccid when cloning dccp sock CVE-2021-40490: ext4: fix race writing to an inline_data file while its xattrs are changing CVE-2020-3702: ath: Use safer key clearing with key cache entries CVE-2021-3655: sctp: validate from_addr_param return added commits: CIP: Bump version suffix to -cip63 after merge from stable Best regards, Nobuhiro
WARNING: multiple messages have this Message-ID (diff)
From: "Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp> To: <cip-dev@lists.cip-project.org> Cc: <pavel@denx.de>, <jan.kiszka@siemens.com>, <Chris.Paterson2@renesas.com>, <uli@fpond.eu>, <masami.ichikawa@cybertrust.co.jp> Subject: [cip-dev] [ANNOUNCE] Release v4.4.285-cip63 Date: Mon, 4 Oct 2021 08:15:20 +0000 [thread overview] Message-ID: <TYAPR01MB6252C6286EDCA87D7DB8B10892AE9@TYAPR01MB6252.jpnprd01.prod.outlook.com> (raw) Message-ID: <20211004081520.39LEmgfJVzh4h9bstgIB0J5y9780T9W7bujUgcjnvYo@z> (raw) [-- Attachment #1: Type: text/plain, Size: 832 bytes --] Hi all, CIP kernel team has released Linux kernel v4.4.285-cip63. The linux-4.4.y-cip tree has been updated from v4.4.283 to v4.4.285. The release information is shown below. v4.4.285-cip63: repository: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git branch: linux-4.4.y-cip commit hash: 18016d4e60e0ab15de4683f6caf64b6289612ac6 Fixed CVEs: CVE-2020-16119: dccp: don't duplicate ccid when cloning dccp sock CVE-2021-40490: ext4: fix race writing to an inline_data file while its xattrs are changing CVE-2020-3702: ath: Use safer key clearing with key cache entries CVE-2021-3655: sctp: validate from_addr_param return added commits: CIP: Bump version suffix to -cip63 after merge from stable Best regards, Nobuhiro [-- Attachment #2: Type: text/plain, Size: 429 bytes --] -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#6770): https://lists.cip-project.org/g/cip-dev/message/6770 Mute This Topic: https://lists.cip-project.org/mt/86061603/4520388 Group Owner: cip-dev+owner@lists.cip-project.org Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/10495289/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org] -=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2021-10-04 8:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-04 8:15 nobuhiro1.iwamatsu [this message] 2021-10-04 8:15 ` [cip-dev] [ANNOUNCE] Release v4.4.285-cip63 Nobuhiro Iwamatsu
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=TYAPR01MB6252C6286EDCA87D7DB8B10892AE9@TYAPR01MB6252.jpnprd01.prod.outlook.com \ --to=nobuhiro1.iwamatsu@toshiba.co.jp \ --cc=Chris.Paterson2@renesas.com \ --cc=cip-dev@lists.cip-project.org \ --cc=jan.kiszka@siemens.com \ --cc=masami.ichikawa@cybertrust.co.jp \ --cc=pavel@denx.de \ --cc=uli@fpond.eu \ /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: linkBe 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).