similar to: [PATCH v1 0/5] clean up block_commit_write

Changelog: v1--v2: 1. Re-order patches to avoid breaking compilation. Bean Huo (5): fs/buffer: clean up block_commit_write ext4: No need to check return value of block_commit_write() fs/ocfs2: No need to check return value of block_commit_write() udf: No need to check return value of block_commit_write() fs/buffer.c: convert block_commit_write to return void fs/buffer.c

On Sun 18-06-23 23:32:48, Bean Huo wrote: > From: Bean Huo <beanhuo at micron.com> > > Remove unnecessary check on the return value of block_commit_write(). > > Signed-off-by: Bean Huo <beanhuo at micron.com> Looks good to me. Feel free to add: Reviewed-by: Jan Kara <jack at suse.cz> Honza > --- > fs/ext4/move_extent.c | 7 ++----- > 1 file

The patch titled Subject: fs: convert block_commit_write to return void has been added to the -mm mm-unstable branch. Its filename is fs-convert-block_commit_write-to-return-void.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/fs-convert-block_commit_write-to-return-void.patch This patch will later appear in the

I was wondering if any one else is having issues with supplementary groups not being recognized. It seems as if Samba is ignoring the sup.groups. I'm using RH9.0 on Intel with samba-3.0.0-2_rh9 and OpenLDAP 2.0.27. When I do a "id -a username" the user is in all the necessary groups but when accessing shares the users' primary GID is used only. For example, uid=1001(jgray)

Anyone have any experience getting ghost to do a successful image with CentOS, Fedora, or RHEL? It worked great with RH9, but now a days I find it nearly impossible to get it to work properly. Any tips would be helpful. We spin up a large number of servers on a weekly basis and it would be nice to just be able to image them. Thanks, -Drew -------------- next part -------------- An HTML

Hi, We have 2 UPS Chloride 80 NET 120 ( a black and white one ) in our datacenter. Could you please tell me if it is possible to use upsmon or other free solution with these two UPS for shuting down servers during electrical lost power before battery crash . Beet regards, Roger -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Sun 18-06-23 23:32:47, Bean Huo wrote: > From: Bean Huo <beanhuo at micron.com> > > block_commit_write() always returns 0, this patch changes it to > return void. > > Signed-off-by: Bean Huo <beanhuo at micron.com> Looks good to me but you'll need to reorder this patch at the end of the patch series to avoid breaking compilation in the middle of the series.

The patch titled Subject: fs/buffer: clean up block_commit_write has been added to the -mm mm-unstable branch. Its filename is fs-buffer-clean-up-block_commit_write.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/fs-buffer-clean-up-block_commit_write.patch This patch will later appear in the mm-unstable branch

On Sun 18-06-23 23:32:46, Bean Huo wrote: > From: Bean Huo <beanhuo at micron.com> > > Originally inode is used to get blksize, after commit 45bce8f3e343 > ("fs/buffer.c: make block-size be per-page and protected by the page lock"), > __block_commit_write no longer uses this parameter inode, this patch is to > remove inode and clean up block_commit_write. >

The patch titled Subject: fs-buffer-clean-up-block_commit_write-fix has been added to the -mm mm-unstable branch. Its filename is fs-buffer-clean-up-block_commit_write-fix.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/fs-buffer-clean-up-block_commit_write-fix.patch This patch will later appear in the

On Sun 18-06-23 23:32:49, Bean Huo wrote: > From: Bean Huo <beanhuo at micron.com> > > Remove unnecessary check on the return value of block_commit_write(). > > Signed-off-by: Bean Huo <beanhuo at micron.com> Looks good to me. Feel free to add: Reviewed-by: Jan Kara <jack at suse.cz> Honza > --- > fs/ocfs2/file.c | 7 +------ > 1 file

On Sun 18-06-23 23:32:50, Bean Huo wrote: > From: Bean Huo <beanhuo at micron.com> > > Remove unnecessary check on the return value of block_commit_write(). > > Signed-off-by: Bean Huo <beanhuo at micron.com> Looks good to me. Feel free to add: Reviewed-by: Jan Kara <jack at suse.cz> Honza > --- > fs/udf/file.c | 6 +++--- > 1 file changed,

On Mon, Jun 19, 2023 at 11:18:24PM +0200, Bean Huo wrote: > From: Bean Huo <beanhuo at micron.com> > > Remove unnecessary check on the return value of block_commit_write(), > because it always returns 0. > > Signed-off-by: Bean Huo <beanhuo at micron.com> > Reviewed-by: Jan Kara <jack at suse.cz> Acked-by: Theodore Ts'o <tytso at mit.edu>

Found 15 patches (out of 162) that appeared relevant to ocfs2 1.4. Please review. Sunil

I was running the previous version of UFO, the 3.3 one that was based on Swift 1.4.8. Now there is a 3.3.1 based on Swift 1.7.4. The config that I used last time to enable S3 isn't working with the new one, just updated yesterday using yum. I was using tempauth in the old version and I'm still using tempauth. I have a CentOS 6 system and a Fedora 18 system with UFO on them. The

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

Hi all. We developped a pv-scsi driver that we refered Fujita-san''s scsi-driver and blkback. (see, http://www.xensource.com/files/xensummit_4/Xen_Summit_8_Matsumoto.pdf) The pv-scsi driver''s feature is as follow: * Guest has dedicated SCSI-HBAs of Dom0. * Guest can send scsi_cdb to the HBAs. * Guest recognises the HBAs from hostno of xenstore. Currentlly, We are

Hi LLVM-ers, I'd like to eliminate dead loop with floating point counter using LLVM, but the following loop wasn't optimized by opt. void func() { float i; for (i = 0.0f; i < 1000.0f; i += 1.2f) { } } $ clang -emit-llvm-bc floop.c $ opt -std-compile-opts floop.bc | llvm-dis define void @func(...) nounwind { entry: br label %forinc forinc: ; preds = %forinc, %entry

Hi Devang, Thanks. Yes, in the case variable i incremented by 1.0f is optimized. I don't know why... Anyway, I've filed this problem into bugzilla(Bug 3299) -- Syoyo On Fri, Jan 9, 2009 at 12:42 AM, Devang Patel <dpatel at apple.com> wrote: > > On Jan 8, 2009, at 4:36 AM, Syoyo Fujita wrote: > >> Hi LLVM-ers, >> >> I'd like to eliminate dead loop

Hi all, Here''s a work in progress series whcih does a partial revert of the previous swiotlb changes, and does a partial replacement with Becky Bruce''s series. The most important difference is Becky''s use of phys_addr_t rather than page+offset to represent arbitrary pages. This turns out to be simpler. I didn''t replicate the map_single_page changes, since