search for: heme

Displaying 20 results from an estimated 82 matches for "heme".

Did you mean: theme
2023 Apr 03
1
fs/ocfs2/super.c:1809 ocfs2_mount_volume() warn: missing error code 'status'
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 7b50567bdcad8925ca1e075feb7171c12015afd1 commit: 0737e01de9c411e4db87dcedf4a9789d41b1c5c1 ocfs2: ocfs2_mount_volume does cleanup job before return error config: arm64-randconfig-m041-20230329 (https://download.01.org/0day-ci/archive/20230401/202304012244.gX4H4rBO-lkp at intel.com/config) compiler:
2023 Apr 30
3
[PATCH 2/2] ocfs2: add error handling path when jbd2 enter ABORT status
fstest generic cases 347 361 628 629 trigger a same issue: When jbd2 enter ABORT status, ocfs2 ignores it and keep going to commit journal. This commit gives ocfs2 ability to handle jbd2 ABORT case. Signed-off-by: Heming Zhao <heming.zhao at suse.com> --- fs/ocfs2/alloc.c | 10 ++++++---- fs/ocfs2/journal.c | 5 +++++ fs/ocfs2/localalloc.c | 3 +++ 3 files changed, 14
2023 Apr 22
1
[PATCH] ocfs2: fix missing reset j_num_trans for sync
Sorry, please pause this patch review. When I was investigating fstest generic failed case 347 361, I found the wake_up() action should move out the 'if()' area. The correct way is calling wake_up() unconditionally. Thanks, Heming On 4/21/23 4:36 PM, Heming Zhao wrote: > fstest generic case 266 272 281 trigger hanging issue when umount. > > I use 266 to describe the root cause.
2009 Dec 31
2
[LLVMdev] How does JIT/lli work with bc file?
Hi Eli, Thanks for your reply. If I add -force-interpreter to lli, then it seems that it can not run external function like printf or malloc. Is there any easy way to solve this problem? On Wed, Dec 30, 2009 at 11:26 PM, Eli Friedman <eli.friedman at gmail.com>wrote: > On Wed, Dec 30, 2009 at 7:53 PM, Heming Cui <heming at cs.columbia.edu> > wrote: > > Dear all, >
2009 Dec 31
3
[LLVMdev] How does JIT/lli work with bc file?
Dear all, I hope you enjoy your christmas! Recently I started to play lli with bc. I found that the lli only calls the main() function in bc file and then does nothing before the main() function returns, which means that the JIT::runFunction() function is involved only once with the main() function in bc file. If this was true, then lli does not have any control to the execution of program.
2009 Dec 31
0
[LLVMdev] How does JIT/lli work with bc file?
On Wed, Dec 30, 2009 at 7:53 PM, Heming Cui <heming at cs.columbia.edu> wrote: > Dear all, >      I hope you enjoy your christmas! Recently I started to play lli with > bc. I found that the lli only calls the main() function in bc file and then > does nothing before the main() function returns, which means that the > JIT::runFunction() function is involved only once with the
2023 Feb 24
1
report BUG: io_uring triggers umount error
On 2/24/23 3:48 PM, Heming Zhao via Ocfs2-devel wrote: > On 2/24/23 2:54 PM, Joseph Qi wrote: >> I can reproduce this in my local VM. >> I've traced ocfs2_dismount_volume and found that it hasn't been called. >> So EBUSY is returned in VFS layer. I guess something wrong when doing >> a copy with linked SQEs (normal copy seems no problem). >> > > I am
2023 Feb 27
2
report BUG: io_uring triggers umount error
On 2/26/23 11:22 PM, Heming Zhao wrote: > On Sun, Feb 26, 2023 at 04:45:44PM +0800, Heming Zhao via Ocfs2-devel wrote: >> On Fri, Feb 24, 2023 at 06:59:47PM +0800, Joseph Qi wrote: >>> >>> >>> On 2/24/23 4:03 PM, Heming Zhao wrote: >>>> On 2/24/23 3:52 PM, Joseph Qi wrote: >>>>> >>>>> >>>>> On 2/24/23 3:48
2023 Feb 24
1
report BUG: io_uring triggers umount error
On 2/24/23 2:54 PM, Joseph Qi wrote: > I can reproduce this in my local VM. > I've traced ocfs2_dismount_volume and found that it hasn't been called. > So EBUSY is returned in VFS layer. I guess something wrong when doing > a copy with linked SQEs (normal copy seems no problem). > I am inclined to agree with you. I also test liburing examples apps on ext4 partition,
2023 Mar 01
1
report BUG: io_uring triggers umount error
Hi, On 2/27/23 10:59 AM, Joseph Qi via Ocfs2-devel wrote: > > > On 2/26/23 11:22 PM, Heming Zhao wrote: >> On Sun, Feb 26, 2023 at 04:45:44PM +0800, Heming Zhao via Ocfs2-devel wrote: >>> On Fri, Feb 24, 2023 at 06:59:47PM +0800, Joseph Qi wrote: >>>> >>>> >>>> On 2/24/23 4:03 PM, Heming Zhao wrote: >>>>> On 2/24/23 3:52
2023 Apr 21
2
[PATCH] ocfs2: Fix wrong search logic in __ocfs2_resv_find_window
Hi, Could you please share a reproducer? Thanks, Joseph On 4/6/23 11:40 PM, Heming Zhao wrote: > ** problem ** > > Current code triggers a defragfs bug [1]: > > ``` > tw-tst:~ # defragfs.ocfs2 /mnt/test_from_dd1 > defragfs.ocfs2 1.8.7 > [ERROR]Move extent failed:"/mnt/test_from_dd1" - No space left on device > [ERROR]"/mnt/test_from_dd1":No space
2023 Feb 26
1
report BUG: io_uring triggers umount error
On Sun, Feb 26, 2023 at 04:45:44PM +0800, Heming Zhao via Ocfs2-devel wrote: > On Fri, Feb 24, 2023 at 06:59:47PM +0800, Joseph Qi wrote: > > > > > > On 2/24/23 4:03 PM, Heming Zhao wrote: > > > On 2/24/23 3:52 PM, Joseph Qi wrote: > > >> > > >> > > >> On 2/24/23 3:48 PM, Heming Zhao via Ocfs2-devel wrote: > > >>> On
2023 Feb 24
1
report BUG: io_uring triggers umount error
On 2/24/23 3:52 PM, Joseph Qi wrote: > > > On 2/24/23 3:48 PM, Heming Zhao via Ocfs2-devel wrote: >> On 2/24/23 2:54 PM, Joseph Qi wrote: >>> I can reproduce this in my local VM. >>> I've traced ocfs2_dismount_volume and found that it hasn't been called. >>> So EBUSY is returned in VFS layer. I guess something wrong when doing >>> a copy
2023 Feb 26
1
report BUG: io_uring triggers umount error
On Fri, Feb 24, 2023 at 06:59:47PM +0800, Joseph Qi wrote: > > > On 2/24/23 4:03 PM, Heming Zhao wrote: > > On 2/24/23 3:52 PM, Joseph Qi wrote: > >> > >> > >> On 2/24/23 3:48 PM, Heming Zhao via Ocfs2-devel wrote: > >>> On 2/24/23 2:54 PM, Joseph Qi wrote: > >>>> I can reproduce this in my local VM. > >>>>
2009 Dec 31
0
[LLVMdev] How does JIT/lli work with bc file?
On Thu, Dec 31, 2009 at 2:26 AM, Heming Cui <heming at cs.columbia.edu> wrote: > Hi Eli, >     Thanks for your reply. If I add -force-interpreter to lli, then it seems > that it can not run external function like printf or malloc. Is there any > easy way to solve this problem? Does the LLVM configure find libffi? -Eli
2010 Jan 01
1
[LLVMdev] How does JIT/lli work with bc file?
Hi Eli, I think the llvm configure has already configured with ffi. ../llvm-2.6/configure -help | grep ffi --enable-libffi Check for the presence of libffi (default is YES) In addition, the printf() can work in program, reflecting that libffi is working, right? How can I make Interpreter work with getpid(), fork(), and clone()? On Thu, Dec 31, 2009 at 2:33 AM, Eli
2023 Feb 24
1
report BUG: io_uring triggers umount error
I can reproduce this in my local VM. I've traced ocfs2_dismount_volume and found that it hasn't been called. So EBUSY is returned in VFS layer. I guess something wrong when doing a copy with linked SQEs (normal copy seems no problem). Thanks, Joseph On 2/24/23 8:32 AM, Heming Zhao wrote: > Hello List, > > I found a weird bug on ocfs2. I am busying with other jobs, if anyone
2023 Apr 21
1
[PATCH] ocfs2: fix missing reset j_num_trans for sync
fstest generic case 266 272 281 trigger hanging issue when umount. I use 266 to describe the root cause. ``` 49 _dmerror_unmount 50 _dmerror_mount 51 52 echo "Compare files" 53 md5sum $testdir/file1 | _filter_scratch 54 md5sum $testdir/file2 | _filter_scratch 55 56 echo "CoW and unmount" 57 sync 58 _dmerror_load_error_table 59 urk=$($XFS_IO_PROG -f -c "pwrite
2023 May 09
1
[PATCH 2/2] ocfs2: add error handling path when jbd2 enter ABORT status
On 5/9/23 12:40 AM, Heming Zhao wrote: > Sorry for reply late, I am a little bit busy recently. > > On Fri, May 05, 2023 at 11:42:51AM +0800, Joseph Qi wrote: >> >> >> On 5/5/23 12:20 AM, Heming Zhao wrote: >>> On Thu, May 04, 2023 at 05:41:29PM +0800, Joseph Qi wrote: >>>> >>>> >>>> On 5/4/23 4:02 PM, Heming Zhao wrote:
2023 Feb 20
1
[PATCH v2] ocfs2: fix non-auto defrag path not working issue
On 2/20/23 1:05 PM, Heming Zhao wrote: > This fixes three issues on move extents ioctl without auto defrag: > > a) In ocfs2_find_victim_alloc_group(), we have to convert bits to block > first in case of global bitmap. > b) In ocfs2_probe_alloc_group(), when finding enough bits in block group > bitmap, we have to back off move_len to start pos as well, otherwise it > may