summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2024-03-14Version Up to fix overlayfs smack deny issuetizen_studio_6.0_p9.0Seung-Woo Kim2-1/+7
Change-Id: I5fd6228072c5e18f13f046cd24a8e432e49270d2 Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2024-03-13ovl: do operations on underlying file system in mounter's contextVivek Goyal3-34/+66
Given we are now doing checks both on overlay inode as well underlying inode, we should be able to do checks and operations on underlying file system using mounter's context. So modify all operations to do checks/operations on underlying dentry/inode in the context of mounter. Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> [sw0312.kim: backport upstream commit 1175b6b8d96331676f1d436b089b965807f23b4a to resolve overlayfs smack deny issue] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I550e2ed212f8a3a578cc48430556fa2c7e1eb3a2
2024-02-23ovl: modify ovl_permission() to do checks on two inodesVivek Goyal1-0/+13
commit c0ca3d70e8d3cf81e2255a217f7ca402f5ed0862 upstream. Right now ovl_permission() calls __inode_permission(realinode), to do permission checks on real inode and no checks are done on overlay inode. Modify it to do checks both on overlay inode as well as underlying inode. Checks on overlay inode will be done with the creds of calling task while checks on underlying inode will be done with the creds of mounter. Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> [ Srivatsa: 4.4.y backport: - Skipped the hunk modifying non-existent function ovl_get_acl() - Adjusted the error path - Included linux/cred.h to get prototype for revert_creds() ] Signed-off-by: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> [sw0312.kim: cherry-pick linux-4.4.y commit b24be4acd17a to fix smack deny issue on overlayfs] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I7cdf2f9136a916c844373be56f84dfc23b8d3bcf
2024-02-23ovl: fix uid/gid when creating over whiteoutMiklos Szeredi1-2/+11
[ Upstream commit d0e13f5bbe4be7c8f27736fc40503dcec04b7de0 ] Fix a regression when creating a file over a whiteout. The new file/directory needs to use the current fsuid/fsgid, not the ones from the mounter's credentials. The refcounting is a bit tricky: prepare_creds() sets an original refcount, override_creds() gets one more, which revert_cred() drops. So 1) we need to expicitly put the mounter's credentials when overriding with the updated one 2) we need to put the original ref to the updated creds (and this can safely be done before revert_creds(), since we'll still have the ref from override_creds()). Reported-by: Stephen Smalley <sds@tycho.nsa.gov> Fixes: 3fe6e52f0626 ("ovl: override creds with the ones from the superblock mounter") Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> Signed-off-by: Sasha Levin (Microsoft) <sashal@kernel.org> [sw0312.kim: cherry-pick linux-4.4.y commit 54a07fff4b21 to fix smack deny issue on overlayfs] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I20e6184091fd96a3fcd9aea8c8026f5532795cd3
2024-02-23ovl: proper cleanup of workdirMiklos Szeredi3-2/+65
commit eea2fb4851e9dcbab6b991aaf47e2e024f1f55a0 upstream. When mounting overlayfs it needs a clean "work" directory under the supplied workdir. Previously the mount code removed this directory if it already existed and created a new one. If the removal failed (e.g. directory was not empty) then it fell back to a read-only mount not using the workdir. While this has never been reported, it is possible to get a non-empty "work" dir from a previous mount of overlayfs in case of crash in the middle of an operation using the work directory. In this case the left over state should be discarded and the overlay filesystem will be consistent, guaranteed by the atomicity of operations on moving to/from the workdir to the upper layer. This patch implements cleaning out any files left in workdir. It is implemented using real recursion for simplicity, but the depth is limited to 2, because the worst case is that of a directory containing whiteouts under "work". Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> Cc: <stable@vger.kernel.org> Signed-off-by: SZ Lin (林上智) <sz.lin@moxa.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> [sw0312.kim: cherry-pick linux-4.4.y commit 89f15c6e8212 to fix smack deny issue on overlayfs] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I34bffb51bab8ce882cf6115e5de108c838bca43f
2024-02-23ovl: override creds with the ones from the superblock mounterAntonio Murdaca5-99/+27
commit 3fe6e52f062643676eb4518d68cee3bc1272091b upstream. In user namespace the whiteout creation fails with -EPERM because the current process isn't capable(CAP_SYS_ADMIN) when setting xattr. A simple reproducer: $ mkdir upper lower work merged lower/dir $ sudo mount -t overlay overlay -olowerdir=lower,upperdir=upper,workdir=work merged $ unshare -m -p -f -U -r bash Now as root in the user namespace: \# touch merged/dir/{1,2,3} # this will force a copy up of lower/dir \# rm -fR merged/* This ends up failing with -EPERM after the files in dir has been correctly deleted: unlinkat(4, "2", 0) = 0 unlinkat(4, "1", 0) = 0 unlinkat(4, "3", 0) = 0 close(4) = 0 unlinkat(AT_FDCWD, "merged/dir", AT_REMOVEDIR) = -1 EPERM (Operation not permitted) Interestingly, if you don't place files in merged/dir you can remove it, meaning if upper/dir does not exist, creating the char device file works properly in that same location. This patch uses ovl_sb_creator_cred() to get the cred struct from the superblock mounter and override the old cred with these new ones so that the whiteout creation is possible because overlay is wrong in assuming that the creds it will get with prepare_creds will be in the initial user namespace. The old cap_raise game is removed in favor of just overriding the old cred struct. This patch also drops from ovl_copy_up_one() the following two lines: override_cred->fsuid = stat->uid; override_cred->fsgid = stat->gid; This is because the correct uid and gid are taken directly with the stat struct and correctly set with ovl_set_attr(). Signed-off-by: Antonio Murdaca <runcom@redhat.com> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> Signed-off-by: SZ Lin (林上智) <sz.lin@moxa.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> [sw0312.kim: cherry-pick linux-4.4.y commit 121b09d30d48 to fix smack deny issue on overlayfs] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I90f9bff54b340cbcc0acc5607c62a7523c66eb92
2024-02-23ovl: rename is_merge to is_lowestMiklos Szeredi1-8/+8
commit 56656e960b555cb98bc414382566dcb59aae99a2 upstream. The 'is_merge' is an historical naming from when only a single lower layer could exist. With the introduction of multiple lower layers the meaning of this flag was changed to mean only the "lowest layer" (while all lower layers were being merged). So now 'is_merge' is inaccurate and hence renaming to 'is_lowest' Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> Signed-off-by: SZ Lin (林上智) <sz.lin@moxa.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> [sw0312.kim: cherry-pick linux-4.4.y commit 6586f61ab5bb to fix smack deny issue on overlayfs] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I00655e4e8286d2d0e16b61e6d11e559c60ec4036
2024-02-23ovl: warn instead of error if d_type is not supportedVivek Goyal1-5/+7
commit e7c0b5991dd1be7b6f6dc2b54a15a0f47b64b007 upstream. overlay needs underlying fs to support d_type. Recently I put in a patch in to detect this condition and started failing mount if underlying fs did not support d_type. But this breaks existing configurations over kernel upgrade. Those who are running docker (partially broken configuration) with xfs not supporting d_type, are surprised that after kernel upgrade docker does not run anymore. https://github.com/docker/docker/issues/22937#issuecomment-229881315 So instead of erroring out, detect broken configuration and warn about it. This should allow existing docker setups to continue working after kernel upgrade. Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> Fixes: 45aebeaf4f67 ("ovl: Ensure upper filesystem supports d_type") Cc: <stable@vger.kernel.org> 4.6 Signed-off-by: SZ Lin (林上智) <sz.lin@moxa.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> [sw0312.kim: cherry-pick linux-4.4.y commit 7eaa995c75bd to fix smack deny issue on overlayfs] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I00157d6950ea475852a59259ff2dbd9cb06c9837
2024-02-23ovl: Do d_type check only if work dir creation was successfulVivek Goyal1-8/+11
commit 21765194cecf2e4514ad75244df459f188140a0f upstream. d_type check requires successful creation of workdir as iterates through work dir and expects work dir to be present in it. If that's not the case, this check will always return d_type not supported even if underlying filesystem might be supporting it. So don't do this check if work dir creation failed in previous step. Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> Signed-off-by: SZ Lin (林上智) <sz.lin@moxa.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> [sw0312.kim: cherry-pick linux-4.4.y commit 0f9a6d88cd9f to fix smack deny issue on overlayfs] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: If7e17d5c56d0fe36762795d582971253ca7118bb
2024-02-23ovl: Ensure upper filesystem supports d_typeVivek Goyal3-0/+53
commit 45aebeaf4f67468f76bedf62923a576a519a9b68 upstream. In some instances xfs has been created with ftype=0 and there if a file on lower fs is removed, overlay leaves a whiteout in upper fs but that whiteout does not get filtered out and is visible to overlayfs users. And reason it does not get filtered out because upper filesystem does not report file type of whiteout as DT_CHR during iterate_dir(). So it seems to be a requirement that upper filesystem support d_type for overlayfs to work properly. Do this check during mount and fail if d_type is not supported. Suggested-by: Dave Chinner <dchinner@redhat.com> Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> Signed-off-by: SZ Lin (林上智) <sz.lin@moxa.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> [sw0312.kim: cherry-pick linux-4.4.y commit d5e678942de3 to fix smack deny issue on overlayfs] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I870cf090c0e52313208718fe87a3e4f7e7a3da08
2024-02-23ovl: filter trusted xattr for non-adminMiklos Szeredi1-1/+11
[ Upstream commit a082c6f680da298cf075886ff032f32ccb7c5e1a ] Filesystems filter out extended attributes in the "trusted." domain for unprivlieged callers. Overlay calls underlying filesystem's method with elevated privs, so need to do the filtering in overlayfs too. Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> Signed-off-by: Sasha Levin <alexander.levin@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> [sw0312.kim: cherry-pick linux-4.4.y commit d88cbbe7ba0c to fix smack deny issue on overlayfs] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I3d7bb51db6e57d16f05fef56d65170aab9bb63f2
2024-02-23ovl: fix failure to fsync lower dirAmir Goldstein1-1/+5
commit d796e77f1dd541fe34481af2eee6454688d13982 upstream. As a writable mount, it is not expected for overlayfs to return EINVAL/EROFS for fsync, even if dir/file is not changed. This commit fixes the case of fsync of directory, which is easier to address, because overlayfs already implements fsync file operation for directories. The problem reported by Raphael is that new PostgreSQL 10.0 with a database in overlayfs where lower layer in squashfs fails to start. The failure is due to fsync error, when PostgreSQL does fsync on all existing db directories on startup and a specific directory exists lower layer with no changes. Reported-by: Raphael Hertzog <raphael@ouaza.com> Signed-off-by: Amir Goldstein <amir73il@gmail.com> Tested-by: Raphaël Hertzog <hertzog@debian.org> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> [sw0312.kim: cherry-pick linux-4.4.y commit 3b0104f9e21a to fix smack deny issue on overlayfs] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: Ieda49c00978f4f26f062a72e83d986d5f97d7f1f
2024-02-07package version up to avoid dibs build conflictChangseok, Oh1-1/+1
2024-01-31Add Tizen-9.0 platformSeung-Woo Kim3-3/+6
Change-Id: I13f638303536810a2b081acea199132d4c06d5eb Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2024-01-25Version Up to fix runtime issue on virtual eepromtizen_studio_5.5_p8.0Seung-Woo Kim2-1/+4
Change-Id: Ic177be5759bdc9141863cb60941ddffee006c2a9 Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2024-01-25maru: eeprom: add missed unlock for EEPROM_SET_WP ioctlSeung-Woo Kim1-1/+2
There was missing unlock during EEPROM_SET_WP ioctl error path. Add the missed unlock. Change-Id: I87c01ab81532058ae93aee10349563e4bdf92b59 Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2024-01-25maru: eeprom: fix crash issue when using eprom ioctl on AMD CPUJianhua Bi1-10/+80
AMD CPU has user memory protection, so direct accessing user address causes memory segment fault. To avoid the crash, use copy_{to/from}_user() for user addresses. Change-Id: I11d88050bfdc712d762c72903e6ca34699b72963 Signed-off-by: Jianhua Bi <jianhua.bi@samsung.com> Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2023-05-17Version Up to fix build with new gcc-12/binutils-2.39Seung-Woo Kim2-1/+4
Change-Id: Ie4beb5427a024884251e4fd075122577fb55e2cd Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2023-05-17maru: Remove useless null checks for array addressSeung-Woo Kim3-13/+0
The array address is always not null, so no need to check. Remove useless null checks to fix -Waddress build warnings. Change-Id: I3bef4644e37d8ed4a2a88fb21408ac1b4ff7a64b Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2023-05-17x86/asm: Add instruction suffixes to bitopsJan Beulich2-14/+17
commit 22636f8c9511245cb3c8412039f1dd95afb3aa59 upstream. Omitting suffixes from instructions in AT&T mode is bad practice when operand size cannot be determined by the assembler from register operands, and is likely going to be warned about by upstream gas in the future (mine does already). Add the missing suffixes here. Note that for 64-bit this means some operations change from being 32-bit to 64-bit. Signed-off-by: Jan Beulich <jbeulich@suse.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Link: https://lkml.kernel.org/r/5A93F98702000078001ABACC@prv-mh.provo.novell.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> [sw0312.kim: cherry-pick stable linux-4.4.y commit eea4429288d to resolve gcc-12 build issue] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: I93b864a6625fcc3e424641e14925c43795b153b6
2023-05-17x86, asm: change the GEN_*_RMWcc() macros to not quote the conditionH. Peter Anvin6-18/+18
commit 18fe58229d80c7f4f138a07e84ba608e1ebd232b upstream. Change the lexical defintion of the GEN_*_RMWcc() macros to not take the condition code as a quoted string. This will help support changing them to use the new __GCC_ASM_FLAG_OUTPUTS__ feature in a subsequent patch. Signed-off-by: H. Peter Anvin <hpa@zytor.com> Link: http://lkml.kernel.org/r/1465414726-197858-4-git-send-email-hpa@linux.intel.com Reviewed-by: Andy Lutomirski <luto@kernel.org> Reviewed-by: Borislav Petkov <bp@suse.de> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> [sw0312.kim: cherry-pick stable linux-4.4.y commit 5be66eab0bbc to resolve gcc-12 build issue] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: Ic11a01ea1195d271f32a3edf038fa86dde355694
2023-05-17scripts/dtc: Remove redundant YYLOC global declarationDirk Mueller2-2/+0
commit e33a814e772cdc36436c8c188d8c42d019fda639 upstream. gcc 10 will default to -fno-common, which causes this error at link time: (.text+0x0): multiple definition of `yylloc'; dtc-lexer.lex.o (symbol from plugin):(.text+0x0): first defined here This is because both dtc-lexer as well as dtc-parser define the same global symbol yyloc. Before with -fcommon those were merged into one defintion. The proper solution would be to to mark this as "extern", however that leads to: dtc-lexer.l:26:16: error: redundant redeclaration of 'yylloc' [-Werror=redundant-decls] 26 | extern YYLTYPE yylloc; | ^~~~~~ In file included from dtc-lexer.l:24: dtc-parser.tab.h:127:16: note: previous declaration of 'yylloc' was here 127 | extern YYLTYPE yylloc; | ^~~~~~ cc1: all warnings being treated as errors which means the declaration is completely redundant and can just be dropped. Signed-off-by: Dirk Mueller <dmueller@suse.com> Signed-off-by: David Gibson <david@gibson.dropbear.id.au> [robh: cherry-pick from upstream] Cc: stable@vger.kernel.org Signed-off-by: Rob Herring <robh@kernel.org> [nc: Also apply to dtc-lexer.lex.c_shipped due to a lack of e039139be8c2, where dtc-lexer.l started being used] Signed-off-by: Nathan Chancellor <natechancellor@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> [sw0312.kim: cherry-pick stable linux-4.4.y commit ce513359d850 to resolve gcc-12 build issue] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: Ica830e72c8227043995560f6f1d5f9918dc28212
2023-05-16Add 8.0sangwook lee3-3/+6
Change-Id: I9eb70830cd285325db04869e05344f9da273e494 Signed-off-by: sangwook lee <sangwook96.lee@samsung.com>
2023-03-23x86: Treat R_X86_64_PLT32 as R_X86_64_PC32tizen_studio_5.5_p7.5H.J. Lu3-0/+5
On i386, there are 2 types of PLTs, PIC and non-PIC. PIE and shared objects must use PIC PLT. To use PIC PLT, you need to load _GLOBAL_OFFSET_TABLE_ into EBX first. There is no need for that on x86-64 since x86-64 uses PC-relative PLT. On x86-64, for 32-bit PC-relative branches, we can generate PLT32 relocation, instead of PC32 relocation, which can also be used as a marker for 32-bit PC-relative branches. Linker can always reduce PLT32 relocation to PC32 if function is defined locally. Local functions should use PC32 relocation. As far as Linux kernel is concerned, R_X86_64_PLT32 can be treated the same as R_X86_64_PC32 since Linux kernel doesn't use PLT. R_X86_64_PLT32 for 32-bit PC-relative branches has been enabled in binutils master branch which will become binutils 2.31. [ hjl is working on having better documentation on this all, but a few more notes from him: "PLT32 relocation is used as marker for PC-relative branches. Because of EBX, it looks odd to generate PLT32 relocation on i386 when EBX doesn't have GOT. As for symbol resolution, PLT32 and PC32 relocations are almost interchangeable. But when linker sees PLT32 relocation against a protected symbol, it can resolved locally at link-time since it is used on a branch instruction. Linker can't do that for PC32 relocation" but for the kernel use, the two are basically the same, and this commit gets things building and working with the current binutils master - Linus ] Signed-off-by: H.J. Lu <hjl.tools@gmail.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> [backport upstream commit b21ebf2fb4cd to support R_X86_64_PLT32 relocation] Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Change-Id: Ieba707440063ceace73758f21adf92c36c068d03
2023-02-22VersionUpsangwook lee2-2/+2
Change-Id: I1515cd363eba32ce41c0bf7b3bd07ceed99593b6 Signed-off-by: sangwook lee <sangwook96.lee@samsung.com>
2023-02-22VersionUpsangwook lee3-3/+6
Change-Id: I1694f2fa2470f6fd39ef6dad9aed29f63e628dd0 Signed-off-by: sangwook lee <sangwook96.lee@samsung.com>
2022-07-01Version Up to fix 64bit kernel issue built by ubuntu 20.04tizen_studio_5.0_p7.0Chanwoo Choi2-1/+4
Change-Id: I14d9cff87600ce745b0592b77edf30dc7ff41ac6 Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
2022-07-01x86/build/64: Force the linker to use 2MB page sizeH.J. Lu1-0/+9
commit e3d03598e8ae7d195af5d3d049596dec336f569f upstream. Binutils 2.31 will enable -z separate-code by default for x86 to avoid mixing code pages with data to improve cache performance as well as security. To reduce x86-64 executable and shared object sizes, the maximum page size is reduced from 2MB to 4KB. But x86-64 kernel must be aligned to 2MB. Pass -z max-page-size=0x200000 to linker to force 2MB page size regardless of the default page size used by linker. Tested with Linux kernel 4.15.6 on x86-64. Signed-off-by: H.J. Lu <hjl.tools@gmail.com> Cc: Andy Shevchenko <andy.shevchenko@gmail.com> Cc: Eric Biederman <ebiederm@xmission.com> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Juergen Gross <jgross@suse.com> Cc: Kees Cook <keescook@chromium.org> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: http://lkml.kernel.org/r/CAMe9rOp4_%3D_8twdpTyAP2DhONOCeaTOsniJLoppzhoNptL8xzA@mail.gmail.com Signed-off-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Change-Id: Id19a848f2d2979861bb022099a1378fdafa9c59f [cw00.choi: Cherry-pick it from linux-stable (4.4.y branch)] Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
2022-06-23build: Set x86_64 kernel version with x86_64 instead of i386Seung-Woo Kim1-0/+1
From package/build.linux, it builds with build-x86.sh and then with build-x86_64.sh. The build-x86.sh changes extraversion as "-i386" from Makefile, so build-x86_64.sh also has same version. Set extraversion to "-x86_64" from build-x86_64.sh. Change-Id: I3b53a7be2ed5be1173e50ce56c43398031a9f195 Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2022-06-23Version up for 4.4.35.26Chanwoo Choi2-1/+4
Change-Id: I1596ba656127187ad00174bfdf790e25bd645717 Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
2022-04-06VersionUpsangwook lee3-3/+6
Change-Id: I7d110fd9236327db525eb1888c05a3c93e915368 Signed-off-by: sangwook lee <sangwook96.lee@samsung.com>
2022-01-11Version up for disabling ANDROID_LOGGERsubmit/tizen_studio_4.5_p6.5/20220111.085032Chanwoo Choi2-1/+4
Change-Id: I01acab1ceb7e606995ad5f253be342103420e94e Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
2022-01-11x86: tizen_emul_defconfig: Disable ANDROID_LOGGER configurationChanwoo Choi1-1/+1
Change-Id: I01a321275320688b71be37de529f3ee652565ef0 Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
2021-10-20Version up for larger virtual screen dpi rangeSeung-Woo Kim2-1/+4
Change-Id: I4fb7a8c83764bc6d7900e45c1c4fd4cc6dc41954 Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2021-10-19drm/vigs: fix dpi allow rangeSeung-Woo Kim1-5/+6
Fix dpi allow range with 1 to 1000. Also, set min or max value for value in out of the range. Change-Id: I89837120b1d0128f1194c86d323d35ca269ef71e Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2021-09-17Version up to add operation lock to maru_power_supplySeung-Woo Kim2-1/+4
Add operation lock to maru_power_supply with 4.4.35.22 version. Change-Id: I83afe52534f8ec5e84cd786bbe1d28af7becadc1 Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2021-09-17maru: power_supply: add operation lockSeung-Woo Kim1-0/+8
maru power_supply has get and set operations to qemu with virtio queue and they can be called multiple times, but only one flag is used to check virtio queue req & res state. This causes virtio queue req & res wait mechanism cannot wake. Add operation lock to resolve this. Change-Id: Ia9c4549160df8ac86cceb7c478f7f2767c42bcf5 Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com>
2021-09-17Version up to support OVERLAY_FS configChanwoo Choi2-1/+4
Change-Id: I34acb5f5e738cd2d76364a509a0a78a4c5de6e1f Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
2021-07-27x86: configs: tizen_emul_defconfig: Enable OVERLAY_FS configChanwoo Choi1-1/+1
Enable CONFIG_OVERLAY_FS for tizen application space. Change-Id: I554460724be788bbee7b63413d260db18f34564a Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
2021-07-16Remove 32bit host supportKarthik2-2/+5
Change-Id: I14665cae60b2c683d6868353e331e1804ea93800 Signed-off-by: Karthik <kv.bhat@samsung.com>
2021-07-16package: Add missing verison up information for CONFIG_CUSE configChanwoo Choi1-1/+1
Change-Id: Ibd84aa70ea1fd5522f09539e460541e1f9250c57 Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
2021-07-15version up: Enable CONFIG_CUSE configChanwoo Choi1-0/+3
Change-Id: I72d8c61027aac3a3e0fa9f584d86f55c69bf2b0f Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
2021-07-15x86: tizen_emul_defconfig: Enable CONFIG_CUSEsangwook lee1-1/+1
CONFIG_CUSE is required for supporting NPU feature on Tizen 6.5. Change-Id: I369cb92c37ba9877f39a58ed7fa2a6e7ac43db7f Signed-off-by: sangwook lee <sangwook96.lee@samsung.com> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
2021-02-24tizen: change mount option of root partion from RW to ROINSUN PYO1-0/+2
Change-Id: I60547b43b41a9f9c17673fd8d903357f5dcd8855
2021-02-18version upChanwoo Choi2-1/+4
Chagnes from previous version: - Disable SECURITY_SMACK_NETFILTER config Change-Id: Ica9c693af5c5ab3b20a0f1851ba844275b78c524 Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
2021-02-18x86: defconfig: disable SECURITY_SMACK_NETFILTER configChanwoo Choi1-1/+1
Disable SECURITY_SMACK_NETFILTER configuration. Change-Id: Ibeb7c584618a0adc0acda97636b75638fc4c9517 Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
2020-12-19"VersionUp & Tizen version up"sangwook lee3-3/+6
Change-Id: Id345724d0a09a2c9c69b85156c5b6dea7adf68da Signed-off-by: sangwook lee <sangwook96.lee@samsung.com>
2020-07-06Version Up for adding CoreCumping and don't remove git informationtizen_studio_4.0_p6.0sangwook96.lee2-1/+5
Change-Id: I9ae6bd5a0b58c66f2d9597cef9ccb7071e9ebf9a Signed-off-by: sangwook96.lee <sangwook96.lee@samsung.com> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com> (cherry picked from commit 82fe7e5e40816d3aa1579a6836f6b529a92451df)
2020-06-03proc, coredump: add CoreDumping flag to /proc/pid/statusRoman Gushchin2-0/+9
Right now there is no convenient way to check if a process is being coredumped at the moment. It might be necessary to recognize such state to prevent killing the process and getting a broken coredump. Writing a large core might take significant time, and the process is unresponsive during it, so it might be killed by timeout, if another process is monitoring and killing/restarting hanging tasks. We're getting a significant number of corrupted coredump files on machines in our fleet, just because processes are being killed by timeout in the middle of the core writing process. We do have a process health check, and some agent is responsible for restarting processes which are not responding for health check requests. Writing a large coredump to the disk can easily exceed the reasonable timeout (especially on an overloaded machine). This flag will allow the agent to distinguish processes which are being coredumped, extend the timeout for them, and let them produce a full coredump file. To provide an ability to detect if a process is in the state of being coredumped, we can expose a boolean CoreDumping flag in /proc/pid/status. Example: $ cat core.sh #!/bin/sh echo "|/usr/bin/sleep 10" > /proc/sys/kernel/core_pattern sleep 1000 & PID=$! cat /proc/$PID/status | grep CoreDumping kill -ABRT $PID sleep 1 cat /proc/$PID/status | grep CoreDumping $ ./core.sh CoreDumping: 0 CoreDumping: 1 [guro@fb.com: document CoreDumping flag in /proc/<pid>/status] Link: http://lkml.kernel.org/r/20170928135357.GA8470@castle.DHCP.thefacebook.com Link: http://lkml.kernel.org/r/20170920230634.31572-1-guro@fb.com Signed-off-by: Roman Gushchin <guro@fb.com> Cc: Alexander Viro <viro@zeniv.linux.org.uk> Cc: Ingo Molnar <mingo@kernel.org> Cc: Konstantin Khlebnikov <koct9i@gmail.com> Cc: Oleg Nesterov <oleg@redhat.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> [k.lewandowsk: backport mainline commit c643401218 for userspace process managers (eg. resourced) to be able to avoid killing dead processes, breaking crash reports] Signed-off-by: Karol Lewandowski <k.lewandowsk@samsung.com> Change-Id: I5ba2fcbf4f388be752db542e80ebca367dba618c
2020-06-02package: Keep the git information after dibs build without removalChanwoo Choi1-2/+0
Change-Id: I85c33a4f1ba840c2238efcc5b367dadd825f70ef Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-31 11:31:10 +0000