similar to: ext3 and ls in a deletted directory

Displaying 20 results from an estimated 90 matches similar to: "ext3 and ls in a deletted directory"

2003 Jan 16
0
[PATCH] Using qstr in ext3_get_parent()
Hi In ext3_get_parent(), quick string (struct qstr) can do the job, in place of declaring a dentry on stack. Following patch does this and saves few bytes on kernel stack. Thanks, Maneesh namei.c | 69 ++++++++++++++++++++++++++++++---------------------------------- 1 files changed, 33 insertions(+), 36 deletions(-) diff -urN linux-2.5.58-base/fs/ext3/namei.c
2017 Jul 26
2
[PATCH] virtio_blk: fix incorrect message when disk is resized
The message printed on disk resize is incorrect. The following is printed when resizing to 2 GiB: $ truncate -s 1G test.img $ qemu -device virtio-blk-pci,logical_block_size=4096,... (qemu) block_resize drive1 2G virtio_blk virtio0: new size: 4194304 4096-byte logical blocks (17.2 GB/16.0 GiB) The virtio_blk capacity config field is in 512-byte sector units regardless of
2017 Jul 26
2
[PATCH] virtio_blk: fix incorrect message when disk is resized
The message printed on disk resize is incorrect. The following is printed when resizing to 2 GiB: $ truncate -s 1G test.img $ qemu -device virtio-blk-pci,logical_block_size=4096,... (qemu) block_resize drive1 2G virtio_blk virtio0: new size: 4194304 4096-byte logical blocks (17.2 GB/16.0 GiB) The virtio_blk capacity config field is in 512-byte sector units regardless of
2010 Aug 04
6
[PATCH -v2 0/3] jbd2 scalability patches
This version fixes three bugs in the 2nd patch of this series that caused kernel BUG when the system was under race. We weren't accounting with t_oustanding_credits correctly, and there were race conditions caused by the fact the I had overlooked the fact that __jbd2_log_wait_for_space() and jbd2_get_transaction() requires j_state_lock to be write locked. Theodore Ts'o (3): jbd2: Use
2004 Jun 20
2
[PATCH] fixup journal-related ifdef mess
always use the 2.6 variants and fix up for 2.4 under the hood Index: src/journal.c =================================================================== --- src/journal.c (revision 1156) +++ src/journal.c (working copy) @@ -105,9 +105,17 @@ return status; } -#else -#define ocfs_journal_start journal_start -#define ocfs_journal_stop journal_stop + +#define journal_start(journal, nblocks) \ +
2014 Oct 24
3
[LLVMdev] Adding masked vector load and store intrinsics
----- Original Message ----- > From: dag at cray.com > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "Elena Demikhovsky" <elena.demikhovsky at intel.com>, llvmdev at cs.uiuc.edu > Sent: Friday, October 24, 2014 11:56:14 AM > Subject: Re: [LLVMdev] Adding masked vector load and store intrinsics > > Hal Finkel <hfinkel at anl.gov> writes:
2014 May 29
3
[PATCH 0/2] UFS1/2 support series
From: Raphael S. Carvalho <raphael.scarv at gmail.com> Wrote the documentation below. I think it would be good to push the doc to the wiki as soon as the UFS support gets merged. Unix Fast File System (UFS/FFS) 1/2 on Syslinux - (usage/install) ----- There is a confusion about the name of this file system, then I decided to contact the author who replied: "The name has always been
2006 Jul 26
9
zfs questions from Sun customer
Please reply to david.curtis at sun.com ******** Background / configuration ************** zpool will not create a storage pool on fibre channel storage. I''m attached to an IBM SVC using the IBMsdd driver. I have no problem using SVM metadevices and UFS on these devices. List steps to reproduce the problem(if applicable): Build Solaris 10 Update 2 server Attach to an external
2013 Jun 19
1
[PATCH] fs/jbd2: t_updates should increase when start_this_handle() failed in jbd2__journal_restart()
jbd2_journal_restart() would restart a handle. In this function, it calls start_this_handle(). Before calling start_this_handle()?subtract 1 from transaction->t_updates. If start_this_handle() succeeds, transaction->t_updates increases by 1 in it. But if start_this_handle() fails, transaction->t_updates does not increase. So, when commit the handle's transaction in
2014 May 29
3
[PATCH v2 0/2] UFS1/2 support series
From: Raphael S. Carvalho <raphael.scarv at gmail.com> Change since v1: * Fix bug on dentry structure (thank you specification; btw, sarcasm), and consequently a bug on ufs_readdir. * Add readlink support (applied tests for symlinks whose destionation path were stored in blk pointers and the file itself). * Several improvements. Wrote the documentation below. I think it would be good to
2018 Jan 03
1
[PATCH] virtio_blk: print capacity at probe time
Print the capacity of the block device when the driver is probed. Many users expect this since SCSI disks (sd) do it. Moreover, kernel dmesg output is the primary source of troubleshooting information so it's helpful to include the disk size there. The capacity is already printed by virtio_blk when a resize event occurs. Extract the code and reuse it from virtblk_probe(). This patch also
2008 Sep 04
4
[PATCH 0/3] ocfs2: Switch over to JBD2.
ocfs2 currently uses the Journaled Block Device (JBD) for its journaling. This is a very stable and tested codebase. However, JBD is limited by architecture to 32bit block numbers. This means an ocfs2 filesystem is limited to 2^32 blocks. With a 4K blocksize, that's 16TB. People want larger volumes. Fortunately, there is now JBD2. JBD2 adds 64bit block number support and some other
2006 Oct 18
5
ZFS and IBM sdd (vpath)
Hello, I am trying to configure ZFS with IBM sdd. IBM sdd is like powerpath, MPXIO or VxDMP. Here is the error message when I try to create my pool: bash-3.00# zpool create tank /dev/dsk/vpath1a warning: device in use checking failed: No such device internal error: unexpected error 22 at line 446 of ../common/libzfs_pool.c bash-3.00# zpool create tank /dev/dsk/vpath1c cannot open
2010 Sep 10
0
[LLVMdev] SCEV Question
On Sep 9, 2010, at 1:48 PM, David Greene wrote: > LLVM 2.7's ScalarEvolution.cpp has this scary comment: > > // It's tempting to handle inttoptr and ptrtoint as no-ops, however this can > // lead to pointer expressions which cannot safely be expanded to GEPs, > // because ScalarEvolution doesn't respect the GEP aliasing rules when > // simplifying integer
2010 Sep 09
2
[LLVMdev] SCEV Question
LLVM 2.7's ScalarEvolution.cpp has this scary comment: // It's tempting to handle inttoptr and ptrtoint as no-ops, however this can // lead to pointer expressions which cannot safely be expanded to GEPs, // because ScalarEvolution doesn't respect the GEP aliasing rules when // simplifying integer expressions. I think I understand what the comment is saying. If a GEP has
2009 Jul 23
0
[LLVMdev] proposed new rule for getelementptr
Hi Dan, Thanks for reply, it seems that Dan Gohman wrote: > On Jul 23, 2009, at 1:59 AM, Mark Shannon wrote: > >> Hi Dan, >> >> What you are proposing is a major change in the semantics of llvm. >> >> You are taking certain uses of an instruction that have well defined >> behaviour and undefining them. >> >> Have you made any estimate of how
2014 Oct 24
2
[LLVMdev] Adding masked vector load and store intrinsics
----- Original Message ----- > From: "Hal Finkel" <hfinkel at anl.gov> > To: "Elena Demikhovsky" <elena.demikhovsky at intel.com> > Cc: dag at cray.com, llvmdev at cs.uiuc.edu > Sent: Friday, October 24, 2014 8:39:56 AM > Subject: Re: [LLVMdev] Adding masked vector load and store intrinsics > > ----- Original Message ----- > > From:
2011 Oct 18
3
[LLVMdev] GEP instructions: is it possible to reverse-engineer array accesses?
Dear All, As of late I am having a hard time getting my head around how array accesses are translated by Clang into LLVM IR: the often misunderstood GEP instruction. I am trying to reverse-engineer array accesses to discover the number of dimensions and actual indexes of the original, and I am beginning to wonder whether this is possible at all. To illustrate (some of) my troubles, consider
2009 Jul 23
2
[LLVMdev] proposed new rule for getelementptr
On Jul 23, 2009, at 1:59 AM, Mark Shannon wrote: > Hi Dan, > > What you are proposing is a major change in the semantics of llvm. > > You are taking certain uses of an instruction that have well defined > behaviour and undefining them. > > Have you made any estimate of how many peoples' code this may or may > not > break? > > I think this is a *very* bad
2017 Aug 04
0
[PATCH] virtio_blk: fix incorrect message when disk is resized
On Wed, Jul 26, 2017 at 03:32:23PM +0100, Stefan Hajnoczi wrote: > The message printed on disk resize is incorrect. The following is > printed when resizing to 2 GiB: > > $ truncate -s 1G test.img > $ qemu -device virtio-blk-pci,logical_block_size=4096,... > (qemu) block_resize drive1 2G > > virtio_blk virtio0: new size: 4194304 4096-byte logical blocks (17.2