From: "Daniel Sangorrin" <daniel.sangorrin@toshiba.co.jp>
To: <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] Kindly review for kernel config changes
Date: Wed, 22 Jul 2020 02:02:01 +0000 [thread overview]
Message-ID: <OSBPR01MB20536E3ED58AC92C3901B931D0790@OSBPR01MB2053.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <OSYPR01MB5366AE110AC4DD024AEAA976DF780@OSYPR01MB5366.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 3620 bytes --]
Hi Kent,
Let me check if we can use the cip-kernel-config version on ISAR and remove the one in isar-cip-core.
I will also add nftables as a fragment to isar-cip-core until you tell me that it needs long-term support. If it needs long-term support we will have to move it to cip-kernel-config.
Thanks,
Daniel
________________________________________
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> on behalf of Kento Yoshida <kento.yoshida.wz@renesas.com>
Sent: Tuesday, July 21, 2020 5:40 PM
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] Kindly review for kernel config changes
>isar-cip-core and deby share cip-kernel-config configuration files.
>*isar-cip-core still has the configuration files there but conf/machine files with
>USE_CIP_KERNEL_CONFIG = "1" do not use them anymore.
I see. Thank you, Daniel.
But, I'm wondering why conf/machine/qemu-amd64.conf doesn't define USE_CIP_KERNEL_CONFIG = "1".
Do you have any information for this, Dinesh or Venkata?
I think we should reconfirm to add these configs to https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/blob/master/4.19.y-cip/x86/cip_qemu_defconfig.
Or, have you already confirmed to build the image using this?
BR, Kent
>-----Original Message-----
>From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of
>Daniel Sangorrin via lists.cip-project.org
>Sent: Tuesday, July 21, 2020 4:57 PM
>To: cip-dev@lists.cip-project.org
>Subject: Re: [cip-dev] Kindly review for kernel config changes
>
>Hi Kent,
>
>The configuration should go to
>https://gitlab.com/cip-project/cip-kernel/cip-kernel-config not isar-cip-core.
>
>isar-cip-core and deby share cip-kernel-config configuration files.
>*isar-cip-core still has the configuration files there but conf/machine files with
>USE_CIP_KERNEL_CONFIG = "1" do not use them anymore.
>
>Actually that is a nother AI.
>
>Thanks,
>Daniel
>
>________________________________________
>From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> on behalf of
>Kento Yoshida <kento.yoshida.wz@renesas.com>
>Sent: Tuesday, July 21, 2020 4:12 PM
>To: cip-dev@lists.cip-project.org
>Subject: [cip-dev] Kindly review for kernel config changes
>
>Hi,
>
>The security working group need to use "nftables", and it requires to add the
>below kernel configs to work.
>Before merging to the master branch of "isar-cip-core", would you kindly review to
>add the below configs by this Friday, everyone?
>
>--- a/recipes-kernel/linux/files/qemu-amd64_defconfig
>+++ b/recipes-kernel/linux/files/qemu-amd64_defconfig
>@@ -351,3 +351,34 @@ CONFIG_CRYPTO_DEV_CCP=y # CONFIG_XZ_DEC_ARM
>is not set # CONFIG_XZ_DEC_ARMTHUMB is not set # CONFIG_XZ_DEC_SPARC is
>not set
>+CONFIG_NF_TABLES=y
>+CONFIG_NF_TABLES_INET=y
>+CONFIG_NF_TABLES_NETDEV=y
>+CONFIG_NFT_EXTHDR=y
>+CONFIG_NFT_META=y
>+CONFIG_NFT_CT=y
>+CONFIG_NFT_RBTREE=y
>+CONFIG_NFT_HASH=y
>+CONFIG_NFT_COUNTER=y
>+CONFIG_NFT_LOG=y
>+CONFIG_NFT_LIMIT=y
>+CONFIG_NFT_MASQ=y
>+CONFIG_NFT_REDIR=y
>+CONFIG_NFT_NAT=y
>+CONFIG_NFT_QUEUE=y
>+CONFIG_NFT_REJECT=y
>+CONFIG_NFT_REJECT_INET=y
>+CONFIG_NFT_COMPAT=y
>+CONFIG_NFT_CHAIN_ROUTE_IPV4=y
>+CONFIG_NFT_REJECT_IPV4=y
>+CONFIG_NFT_CHAIN_NAT_IPV4=y
>+CONFIG_NFT_MASQ_IPV4=y
>+# CONFIG_NFT_REDIR_IPV4 is not set
>+CONFIG_NFT_CHAIN_ROUTE_IPV6=y
>+CONFIG_NFT_REJECT_IPV6=y
>+CONFIG_NFT_CHAIN_NAT_IPV6=y
>+CONFIG_NFT_MASQ_IPV6=y
>+# CONFIG_NFT_REDIR_IPV6 is not set
>+CONFIG_NFT_BRIDGE_META=y
>+CONFIG_NFT_BRIDGE_REJECT=y
>+CONFIG_NF_LOG_BRIDGE=y
>
>BR, Kent
[-- Attachment #2: Type: text/plain, Size: 419 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4954): https://lists.cip-project.org/g/cip-dev/message/4954
Mute This Topic: https://lists.cip-project.org/mt/75699231/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-07-22 2:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 7:12 [cip-dev] Kindly review for kernel config changes Kento Yoshida
2020-07-21 7:56 ` Daniel Sangorrin
2020-07-21 8:40 ` Kento Yoshida
2020-07-22 2:02 ` Daniel Sangorrin [this message]
2020-08-04 4:12 ` Daniel Sangorrin
2020-08-04 4:12 ` Daniel Sangorrin
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=OSBPR01MB20536E3ED58AC92C3901B931D0790@OSBPR01MB2053.jpnprd01.prod.outlook.com \
--to=daniel.sangorrin@toshiba.co.jp \
--cc=cip-dev@lists.cip-project.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.