summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2019-07-31ARM: artik530_raptor_defconfig: Enable NETFILTER_XT_MATCH_OWNER config optiontizen_5.5.m2_releasesubmit/tizen_5.5_mobile_hotfix/20201026.185109submit/tizen_5.5/20191031.000013submit/tizen_5.5/20191031.000011submit/tizen_5.5/20191031.000010submit/tizen/20190801.010047accepted/tizen/unified/20190801.113434accepted/tizen/5.5/unified/mobile/hotfix/20201027.070457accepted/tizen/5.5/unified/20191031.032438tizen_5.5_tvtizen_5.5_mobile_hotfixaccepted/tizen_5.5_unified_mobile_hotfixSeung-Woo Kim1-1/+1
Enable the NETFILTER_XT_MATCH_OWNER config option to use xt_owner supplementary groups. Change-Id: Id36610567dedf2da808e0b59efe9430ad68df899 Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2019-07-31ARM64: artik710_raptor_defconfig: Enable NETFILTER_XT_MATCH_OWNER config optionSeung-Woo Kim1-1/+1
Enable the NETFILTER_XT_MATCH_OWNER config option to use xt_owner supplementary groups. Change-Id: I5570988cf08cf65c05ee476a6656f8b4f0f0f664 Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2019-07-31netfilter: xt_owner: A fix for backport of 'xt_owner: Add supplementary ↵Lukasz Pawelczyk1-1/+1
groups option' This patch fixes the backport of 'netfilter: xt_owner: Add supplementary groups option' (8413c52116d5). Change-Id: I85fd812744fd95b4c7f4640670a685c033e024ad Signed-off-by: Lukasz Pawelczyk <l.pawelczyk@samsung.com> Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2019-07-05netfilter: xt_owner: bail out with EINVAL in case of unsupported flagssubmit/tizen/20190705.061120accepted/tizen/unified/20190705.110618Pablo Neira Ayuso2-0/+8
Reject flags that are not supported with EINVAL. Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org> [sw0312.kim: backport from mainline to apply supplementary groups on netfilter] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I129a3a1fc8f54d5e4f0ae164e0036bad7cd67c64
2019-07-05netfilter: xt_owner: Add supplementary groups optionLukasz Pawelczyk2-6/+24
The XT_OWNER_SUPPL_GROUPS flag causes GIDs specified with XT_OWNER_GID to be also checked in the supplementary groups of a process. f_cred->group_info cannot be modified during its lifetime and f_cred holds a reference to it so it's safe to use. Signed-off-by: Lukasz Pawelczyk <l.pawelczyk@samsung.com> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org> [sw0312.kim: backport from mainline to apply supplementary groups on netfilter] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I30739d09c47d0623d0638de685905d3ac2ca131a
2019-02-18Revert "arm64: dtsi: artik710_raptor: change default camera image sensor to ↵submit/tizen_5.0/20190219.004732submit/tizen/20190218.062336accepted/tizen/unified/20190218.163151accepted/tizen/5.0/unified/20190219.154237tizen_5.0accepted/tizen_5.0_unifiedSeung-Woo Kim1-12/+9
OV5640" This reverts commit d636f7529dfa0ca074716fd255c9655acbad5d23. In tizen environment, previous camera image sensor, ARTIK-5M- CAMERA-BOARD MM011-0.1 with S5K4ECGA image sensor is still used. So revert OV5640 camera image sensor. Change-Id: I5584de55165be731d1a863c3e3da2e1949fb0663 Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2019-02-18Revert "arm: dtsi: artik530_raptor: change default camera image sensor to ↵Seung-Woo Kim1-13/+10
OV5640" This reverts commit 8fefb8f77d19f0670bc2026f43eb4c6af86d9e3b. In tizen environment, previous camera image sensor, ARTIK-5M- CAMERA-BOARD MM011-0.1 with S5K4ECGA image sensor is still used. So revert OV5640 camera image sensor. Change-Id: I25632c12589238d8fea9924acd7d5bc582c6ecb8 Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2019-01-31usb: dwc2: hcd: call dwc2_is_controller_alive under spinlocksubmit/tizen_5.0/20190213.011623submit/tizen/20190131.075243accepted/tizen/unified/20190131.161530accepted/tizen/5.0/unified/20190213.070121Jaehoon Chung1-3/+4
This patch is referred to Robert's commit cf54772b913b. (usb: dwc2: call dwc2_is_controller_alive() under spinlock) Below is commit message: This patch fixes the following problem: data transmission in direction IN break unless the GSNPSID register access is done with spinlock held. This issue occurs at least in Exynos4412 SoC, probably in many SoC's from Exynos familly. The problem is described here: https://lkml.org/lkml/2014/12/22/185 And there is linux mailing list discussion: https://lkml.org/lkml/2015/1/14/17 The one of SDB hang issues should be fixed with this patch. (Issue - Not triggered usb interrupt.) Change-Id: If97516bc94d84df611663f902267a5e3b75815f7 Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29ARM64: configs: artik710: enable COFIG_VIDEO_OV5640submit/tizen/20190129.052023accepted/tizen/unified/20190130.053716Jaehoon Chung1-1/+1
Enable CONFIG_VIDEO_OV5640 configuration. Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29packaging: spec: update the kernel stable version from 4.4.113 to 4.4.172Jaehoon Chung2-2/+2
Update the kernel stable version from v4.4.113 to 4.4.172. Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29ARM64: config: artik710: update the defconfig file to v4.4.172Jaehoon Chung1-12/+24
Update the defconfig file to v4.4.172. Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29ARM: configs: artik530: update the defconfig file to v4.4.172Jaehoon Chung1-11/+21
Synchronize the defconfig file to v4.4.172. Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29switch ->setxattr() to passing dentry and inode separatelyAl Viro32-82/+105
commit 3767e255b390d72f9a33c08d9e86c5f21f25860f upstream. smack ->d_instantiate() uses ->setxattr(), so to be able to call it before we'd hashed the new dentry and attached it to inode, we need ->setxattr() instances getting the inode as an explicit argument rather than obtaining it from dentry. Similar change for ->getxattr() had been done in commit ce23e64. Unlike ->getxattr() (which is used by both selinux and smack instances of ->d_instantiate()) ->setxattr() is used only by smack one and unfortunately it got missed back then. Reported-by: Seung-Woo Kim <sw0312.kim@samsung.com> Tested-by: Casey Schaufler <casey@schaufler-ca.com> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> [sw0312.kim: backport from mainline to resolve setxattr crash on smack] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I4bf991924e16f61746453b7fd096e5d59438659b
2019-01-29switch xattr_handler->set() to passing dentry and inode separatelyAl Viro27-102/+124
commit 5930122683dff58f0846b0f0405b4bd598a3ba6a upstream. preparation for similar switch in ->setxattr() (see the next commit for rationale). Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> [sw0312.kim: backport from mainline to resolve setxattr issue during smack_d_instantiate()] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I3e2e2cd71ebe14aea7610a6457e68d1fb01ead89
2019-01-29security_d_instantiate(): move to the point prior to attaching dentry to inodeAl Viro1-10/+6
commit b96809173e94ea2fa8c19c2e40e8545a1821bf57 upstream. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> [sw0312.kim: backport from mainline to resolve smack crash issue during getxattr] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: If386ad04e7e1abdd9213df87daf17648eb9f42fd
2019-01-29->getxattr(): pass dentry and inode as separate argumentsAl Viro37-95/+104
commit ce23e640133484eebc20ca7b7668388213e11327 upstream. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> [sw0312.kim: backport from mainline to resolve smack getxattr during security_d_instantiate()] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I7fcd9edc3e3e543e35e173e8479906b6a7f81455
2019-01-29xattr_handler: pass dentry and inode as separate arguments of ->get()Al Viro28-103/+102
commit b296821a7c42fa58baa17513b2b7b30ae66f3336 upstream. ... and do not assume they are already attached to each other Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> [sw0312.kim: backport from mainline to apply getxattr inode separation] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: Ic3f9c370f13ceacda25d20bb7d5b6d732966e648
2019-01-29ASoC: rt5659: fix duplicate‘const’ declaration warningsSeung-Woo Kim1-70/+70
Fix duplicate const’ declaration specifier warnings in gcc 7. Note: macros, SOC_VALUE_ENUM_SINGLE_DECL(), SOC_ENUM_SINGLE_DECL() already have const specifier. Change-Id: Ifc4940cfc38a77802d1c53703f9608c48ce8dbdf Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2019-01-29usb: f_fs: avoid race condition with ffs_epfile_io_completeDu, Changbin1-3/+9
ffs_epfile_io and ffs_epfile_io_complete runs in different context, but there is no synchronization between them. consider the following scenario: 1) ffs_epfile_io interrupted by sigal while wait_for_completion_interruptible 2) then ffs_epfile_io set ret to -EINTR 3) just before or during usb_ep_dequeue, the request completed 4) ffs_epfile_io return with -EINTR In this case, ffs_epfile_io tell caller no transfer success but actually it may has been done. This break the caller's pipe. Below script can help test it (adbd is the process which lies on f_fs). while true do pkill -19 adbd #SIGSTOP pkill -18 adbd #SIGCONT sleep 0.1 done To avoid this, just dequeue the request first. After usb_ep_dequeue, the request must be done or canceled. With this change, we can ensure no race condition in f_fs driver. But actually I found some of the udc driver has analogical issue in its dequeue implementation. For example, 1) the dequeue function hold the controller's lock. 2) before driver request controller to stop transfer, a request completed. 3) the controller trigger a interrupt, but its irq handler need wait dequeue function to release the lock. 4) dequeue function give back the request with negative status, and release lock. 5) irq handler get lock but the request has already been given back. So, the dequeue implementation should take care of this case. IMO, it can be done as below steps to dequeue a already started request, 1) request controller to stop transfer on the given ep. HW know the actual transfer status. 2) after hw stop transfer, driver scan if there are any completed one. 3) if found, process it with real status. if no, the request can canceled. Signed-off-by: "Du, Changbin" <changbin.du@intel.com> [mina86@mina86.com: rebased on top of refactoring commits] Signed-off-by: Michal Nazarewicz <mina86@mina86.com> Signed-off-by: Felipe Balbi <balbi@kernel.org> Signed-off-by: Dongwoo Lee <dwoo08.lee@samsung.com> Change-Id: I12832c8cd8060302eff13565cf2f1372288d07ed
2019-01-29usb: f_fs: refactor ffs_epfile_ioMichal Nazarewicz1-67/+59
Eliminate one of the return paths by using a ‘goto error_mutex’ and rearrange some if-bodies which results in reduction of the indention level and thus hopefully makes the function easier to read and reason about. Signed-off-by: Michal Nazarewicz <mina86@mina86.com> Signed-off-by: Felipe Balbi <balbi@kernel.org> [backported from upstream commit ae76e13477d8de0065cddbb6] Signed-off-by: Dongwoo Lee <dwoo08.lee@samsung.com> Change-Id: Ic8f141faa55ce5c0bad6f55506d30d84feb88c90
2019-01-29fix build error about get_user_pages()Jaehoon Chung2-3/+3
Fix build error since changing the arguments of get_user_pages(). Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29iio: adc: nexell_adc: Fix duplicate ‘const’ declaration specifier build ↵Hoegeun Kwon1-1/+1
warning This patch fixes following build warning caused duplicate declaration: drivers/iio/adc/nexell_adc.c:358:37: warning: duplicate ‘const’ declaration specifier [-Wduplicate-decl-specifier] static const struct nexell_adc_data const nexell_adc_s5p6818_data = { ^~~~~ Change-Id: I5870765ed0700169aac0b5a93beaf79a9110ed58 Signed-off-by: Hoegeun Kwon <hoegeun.kwon@samsung.com>
2019-01-29ARM: dts: s5p4418: add the otg clock value as 12MHzJaehoon Chung1-0/+1
Add the otg clock value as 12MHz. It needs to set same value with usbhost clock value. Change-Id: If293e1082b913e75c70f8358300ca519c3bbd6f7 Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29ARM: dts: s5p4418: fix the register address typoJaehoon Chung1-1/+1
Fix the register address type. According to ARTIK530 TRM, there is no 0x6c00b000 address. Change-Id: I1bfa558fbe0149e61c3bc571035b06839ba40de0 Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29mmc: dw_mmc: fix the wrong pointer typeJaehoon Chung1-1/+1
Fix the wrong types from unsigned int to unsigned long. Change-Id: I24d17685033d7fdbbb8c4e3351dfd8fae1236ef8 Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29soc: nexell: remove the redefined ATTR_MODEJaehoon Chung1-4/+6
ATTR_MODE is already defined in include/linux/fs.h. Instead, use S_IRUSR | S_IRGRP | S_IROTH (0x444) in stat.h Change-Id: Ia22a74ac628ad0899b8aac36c45384aa17f7709c Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29packaging: spec: update the kernel stable versionJaehoon Chung2-2/+2
Update the kernel stable version from 4.4.71 from 4.4.113. Change-Id: I204d73cdc669b4c68e64118ca274710f127aeac6 Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29usb: dwc2: Move definition of ext_vbus_ioDongwoo1-1/+2
There are build errors on ext_vbus_io when the operational mode is set to gadget only mode because it doesn't included by conditional macro. In order to make including ext_vbus_io member for all operational mode, this patch moves ext_vbus_io out of macro section. Change-Id: Ib9a70c2a27cd6afd9969de422f3cbcbe80a2751d Signed-off-by: Dongwoo <dwoo08.lee@samsung.com>
2019-01-29LOCAL / usb: gadget: f_fs: Limit data buffer size to a single pageDongwoo1-0/+8
Large size request from sdbd usually causes memory allocation failure in case of memory shortage. The failure is not handled by sdbd properly and thus it makes sdbd a hung state. To prevent this situation, this patch limits data buffer size to a single page so as to guarantee memory allocation success. * This is WORKAROUND solution for just use case of sdbd, it should be reverted when the advanced dma solution is applied to f_fs * Change-Id: Ib917c3aef2b00a3e00a3d87ca6d6940307038aa1 Signed-off-by: Dongwoo <dwoo08.lee@samsung.com>
2019-01-29usb: dwc2: gadget: set the quirk_ep_out_alinged_size as trueJaehoon Chung1-0/+2
Set the quirk_ep_out_aligned_size as ture. This patch is fixed about occurring kernel panic after failed memory allocation. Change-Id: Iafb6ccaa6f7d7dac4eb0593291166ab13cd8256d Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29ARM64: config: artik710_raptor: enable RT2X00 USB driverJaehoon Chung1-1/+18
Enable RT2X00 usb driver. Change-Id: I8e071a988e2778088e80c5470cb5ff1e612025f4 Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29ARM: config: artik530_raptor: enable RT2X00 USB driverJaehoon Chung1-1/+18
Enable RT2X00 usb driver. Change-Id: I0592f6a6408d2dece89e7e08f03d647449b99f2a Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29ARM64: config: artik710_raptor: enable realtek USB driverJaehoon Chung1-2/+7
Enable Realtek USB driver to test Wifi Mesh. Change-Id: I8a910a11666f7e6a8d8eab5a8ac791ea41648681 Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29ARM: config: artik530_raptor: enable realtek USB driverJaehoon Chung1-2/+7
Enable Realtek USB driver to test WiFi Mesh. Change-Id: I112640eaa46971a2ca958b7d5aea68e9745beff8 Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29ARM: artik710_raptor_defconfig: sync defconfig for usb optionsSeung-Woo Kim1-1/+30
After the commit 3922eabecf08 ("usb: gadget: Allow to build both USB functions and legacy gadgets"), usb options are changed and it is not clear legacy composite gadget is set or not. To clarify, sync defconfig for usb options. Change-Id: Ia2f2f7e121094adfb5745cffbcf3edab243f6810 Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2019-01-29ARM: artik530_raptor_defconfig: Replace legacy composite gadget with ↵Dongwoo Lee1-7/+11
ConfigFS gadget To replace legacy composite USB gadget for SDB, MTP, RNDIS with ConfigFS gadget, this enables ConfigFS/FunctionFS support for USB gadget. Change-Id: I155a788ff6390d496ab047f9cd495aa141bc7d26 Signed-off-by: Dongwoo Lee <dwoo08.lee@samsung.com>
2019-01-29ARM: dts: artik533-compy: add the user gpio-key nodesWooChang Kim1-2/+16
Eagleye board is provided the two user buttons. (Defined them as "backkey" and "wakeup") Change-Id: I524ca8b1b09b65b1c79d136adef02fd6872c6069 Signed-off-by: WooChang Kim <wchang.kim@samsung.com> Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29ARM: dts: artik533-compy: enable the i2c_1 nodeJaehoon Chung1-0/+4
Enable the i2c_1 node. Change-Id: I4aaafbe5cf5cecf2cd06eec80d59c2f004d6036b Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29ARM: dts: arti533-compy: add the nodes relevant to spi/i2c/serialJaehoon Chung1-0/+29
Add the nodes relevant to spi/i2c/serial. Change-Id: Ia578cf93f46c271c3836d8fbb94bcdbda15a77c7 Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29input: touchscreen: add touch enabled nodeJaechul Lee1-36/+89
touchscreen 'enabled' node needs to be supproted on Tizen because deviced wants to handle touchscreen on/off for some reasons. Touch event will be skipped if 'enabled' is 0. Change-Id: I53eac0a5f38c09f326da24a5ee1d5e985d61332c Signed-off-by: Jaechul Lee <jcsing.lee@samsung.com>
2019-01-29Revert "ARM: artik710_raptor_defconfig: Enable DUMMY_HCD module"Dongwoo Lee1-32/+2
Because the change for size of module in the corresponding commit seems to make failure on building boot image for artik710 board, this reverts commit aece406a175adfb8de56c10e1d011ae2c6852cc5. Change-Id: Ia18eaf165f180c39aded417be4a1130ba6edb113 Signed-off-by: Dongwoo Lee <dwoo08.lee@samsung.com>
2019-01-29ARM: artik710_raptor_defconfig: Enable DUMMY_HCD moduleDongwoo Lee1-2/+32
These options enable DUMMY_HCD as a module to support USB test case without real usb hardware. Change-Id: I8ccb30d1cec4baad5dccdd0670039ab203bfbc2c Signed-off-by: Dongwoo Lee <dwoo08.lee@samsung.com>
2019-01-29ARM: artik530_raptor_defconfig: Enable DUMMY_HCD moduleDongwoo Lee1-2/+32
These options enable DUMMY_HCD as a module to support USB test case without real usb hardware. Change-Id: I4b20065a0644a68398ac6b8f2d4c5c96e1af1dd5 Signed-off-by: Dongwoo Lee <dwoo08.lee@samsung.com>
2019-01-29usb: gadget: Allow to build both USB functions and legacy gadgetsKrzysztof Opasiak2-188/+613
Currently it is possible to build in some subset of usb functions *OR* some gadget module. This is limited only by Kconfig not any functionality. This patch removes this limitation. With this patch it is possible to set up all build combinations: 1) Multiple gadgets build in 2) Part of functions build in, part of functions as a modules 3) Some gadgets build in and some part of functions build in/modules etc. As this patch makes Kconfig quite complicated let me clarify how it works: USB_F_<func name> - used in makefile for compilation USB_CONFIGFS_F_<func name> - Chosen by user in function menu USB_G_<gadget name>_REQ_F_<func name> - set up by gadget to mark that this particular gadget requires this func to work USB_F_<func name>_SELECTOR - helper config which is used to determine if function should be build in or compiled as a module The rules are quite simple: 1) If any of USB_CONFIGFS_F_<func name>, USB_G_*_REQ_F_<func name> equals y, then USB_F_<func name> is set to y and function is build in 2) If none of USB_CONFIGFS_F_<func name>, USB_G_*_REQ_F_<func name> equals y, but any of them equals m then USB_F_<func name> is set to m and function is compiled as a module Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> [Backported from commit under review @linux-usb mailing list] Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Signed-off-by: Dongwoo Lee <dwoo08.lee@samsung.com> Change-Id: I86e796d7c057afce163695dc280861477a9f4b56
2019-01-29ARM: configs: artik530_raptor: enable OV5640 camera sensorJaehoon Chung1-0/+1
This patch enables CONFIG_VIDEO_OV5640. Change-Id: I658411faa738295cf88faaa608da795b89fe9fc1 Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29ARM: dts: artik533-compy: Enable extcon notification for usb connectionJaehoon Chung1-0/+1
Eagleye ARTIK530s board is using its own device-tree. This patch is referred to Dongwoo's patches. "arm: dts: artik530_raptor: nable extcon notification for usb connection" Change-Id: I22cfbe37813a9ae3d39706f2a9a205f091e948db Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
2019-01-29ARM64: artik710_raptor_defconfig: enable NETFILTER_XT_TARGET_LOGSeung-Woo Kim1-3/+4
Enable NETFILTER_XT_TARGET_LOG for analysis of iptables log. It is a iptables feature for security report on Tizen 5.0, required from stc-manager. Change-Id: Ice8cbce90b07eb9da9b09812f9306b7c424533c9 Signed-off-by: hyunuktak <hyunuk.tak@samsung.com> Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2019-01-29ARM64: artik710_raptor_defconfig: enable CONFIG_CONNECTOR and CONFIG_PROC_EVENTSSeung-Woo Kim1-1/+3
These options enable Netlink Connector feature of kernel to monitor process lifecycle like Fork and Exit status of all processes asynchronously. In Tzen, it will be used by stc-manager(smart traffic control) to monitor process lifecycle. Change-Id: I265504609e6b2ce963875e66884d064affc48d9d Signed-off-by: hyunuktak <hyunuk.tak@samsung.com> Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2019-01-29ARM: artik530_raptor_defconfig: enable NETFILTER_XT_TARGET_LOGSeung-Woo Kim1-3/+4
Enable NETFILTER_XT_TARGET_LOG for analysis of iptables log. It is a iptables feature for security report on Tizen 5.0, required from stc-manager. Signed-off-by: hyunuktak <hyunuk.tak@samsung.com> Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: Ia31c1e9463f28b74a67bad7272e0fea08c88c28c
2019-01-29ARM: artik530_raptor_defconfig: enable CONFIG_CONNECTOR and CONFIG_PROC_EVENTSSeung-Woo Kim1-1/+3
These options enable Netlink Connector feature of kernel to monitor process lifecycle like Fork and Exit status of all processes asynchronously. In Tzen, it will be used by stc-manager(smart traffic control) to monitor process lifecycle. Change-Id: I62a5ba2830672b9532ed26a3f90011584522a2bc Signed-off-by: hyunuktak <hyunuk.tak@samsung.com> Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-23 15:34:07 +0000