similar to: [PATCH] xfs: Add support for v3 directories

This pull request contains the XFS filesystem driver for Syslinux. Due to historical reasons (SGI IRIX's design of disk layouts), the first sector in the primary AG on XFS filesystems contains the superblock, which is a problem with BIOSes, since VBRs must be loaded up from the first sector of the active partition. Thus, we needed to handle this issue by putting the Syslinux bootsector

xfs_is_valid_magicnum is not actually a generic function that checks for magic numbers, instead it checks only for superblock's one. Signed-off-by: Paulo Alcantara <pcacjr at zytor.com> --- core/fs/xfs/xfs.c | 13 +++++-------- core/fs/xfs/xfs.h | 19 ++++++++++--------- 2 files changed, 15 insertions(+), 17 deletions(-) diff --git a/core/fs/xfs/xfs.c b/core/fs/xfs/xfs.c index

On Mon, January 18, 2016 10:51 am, Gene Cumm wrote: > On Mon, Dec 14, 2015 at 7:54 PM, Paulo Alcantara <pcacjr at gmail.com> wrote: >> Besides supporting newer version of xfs file system, this patch also >> does some code refactoring and fix completely broken listing and >> searching on v2-3 node directories. >> >> Cc: Gene Cumm <gene.cumm at gmail.com>

On Mon, Dec 14, 2015 at 7:54 PM, Paulo Alcantara <pcacjr at gmail.com> wrote: > Besides supporting newer version of xfs file system, this patch also > does some code refactoring and fix completely broken listing and > searching on v2-3 node directories. > > Cc: Gene Cumm <gene.cumm at gmail.com> > Cc: H. Peter Anvin <hpa at zytor.com> > Cc: Raphael S.

Hi.....I am relatively new to R but was quite pleased with myself at having generated a series of lattice plots as PDFs. I was very surprised when plotting these out as jpegs (or png or tiff) that the strip title information above each lattice plot vanished. The pdf was fine. Has anybody any ideas? I can't add an image as the information is sensitive. Many Thanks Steve Creamer Here is the

Hi! I am trying to know which habitat variables most affect bird counts in a radius of 100m. I obtained bird counts in 2751 spatial points, and measured percentage of 21 habitat variables in these points. I applied a mixed model using the "lmer" function to these data, but I do not know how to select the best model using AIC here. Is there a way to do this automatically with R?

Full_Name: Hugh C. Pumphrey Version: 1.4.1 OS: Linux (Debian Woody) Submission from: (NULL) (129.215.133.170) The function readChar() appears to have some type of problem with memory allocation. I don't know if "memory leak" is the correct term but if one uses readChar() many times, the R binary grows in size until it eats all your memory and swap space. The code enclosed below

Hi, Gene Cumm wrote: > > 3) It feels like this is a moving target where gcc keeps changing and > > different results get reported. Do we have indications that different versions of gcc5 cause different behavior on the same build and boot machines ? Ady wrote: > Since the issue is only present on specific > hardware / firmware, whatever might seem to "solve" the

Hi, our dovecot processes sometimes crash when we create new folders. The "imap" process and the "indexer worker" process is crashing. We can reproduce this, we have a java program with multiple threads, and sometimes 2 threads try to create the same folder for the same user, and if both collide, dovecot processes crash. We don't see this happening in the real world if

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> ---

The current memory accessors logic is: - little endian if little_endian - native endian (i.e. no byteswap) if !little_endian If we want to fully support cross-endian vhost, we also need to be able to convert to big endian. Instead of changing the little_endian argument to some 3-value enum, this patch changes the logic to: - little endian if little_endian - big endian if !little_endian The

The current memory accessors logic is: - little endian if little_endian - native endian (i.e. no byteswap) if !little_endian If we want to fully support cross-endian vhost, we also need to be able to convert to big endian. Instead of changing the little_endian argument to some 3-value enum, this patch changes the logic to: - little endian if little_endian - big endian if !little_endian The

The current memory accessors logic is: - little endian if little_endian - native endian (i.e. no byteswap) if !little_endian If we want to fully support cross-endian vhost, we also need to be able to convert to big endian. Instead of changing the little_endian argument to some 3-value enum, this patch changes the logic to: - little endian if little_endian - big endian if !little_endian The

Hello (Timo), depending on the client (with OfflineIMAP, but not a mobile one) my dovecot test configuration (config on request) crashes if mailbox_list_index=yes: Apr 9 09:26:31 host dovecot: imap-login: Login: user=<user>, method=CRAM-MD5, rip=2001:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx, lip=2001:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx, mpid=19028, TLS,

The current memory accessors logic is: - little endian if little_endian - native endian (i.e. no byteswap) if !little_endian If we want to fully support cross-endian vhost, we also need to be able to convert to big endian. Instead of changing the little_endian argument to some 3-value enum, this patch changes the logic to: - little endian if little_endian - big endian if !little_endian The

On Tue, Apr 07, 2015 at 02:15:52PM +0200, Greg Kurz wrote: > The current memory accessors logic is: > - little endian if little_endian > - native endian (i.e. no byteswap) if !little_endian > > If we want to fully support cross-endian vhost, we also need to be > able to convert to big endian. > > Instead of changing the little_endian argument to some 3-value enum, this

On Tue, Apr 07, 2015 at 02:15:52PM +0200, Greg Kurz wrote: > The current memory accessors logic is: > - little endian if little_endian > - native endian (i.e. no byteswap) if !little_endian > > If we want to fully support cross-endian vhost, we also need to be > able to convert to big endian. > > Instead of changing the little_endian argument to some 3-value enum, this

On Fri, Apr 10, 2015 at 12:16:20PM +0200, Greg Kurz wrote: > The current memory accessors logic is: > - little endian if little_endian > - native endian (i.e. no byteswap) if !little_endian > > If we want to fully support cross-endian vhost, we also need to be > able to convert to big endian. > > Instead of changing the little_endian argument to some 3-value enum, this

On Fri, Apr 10, 2015 at 12:16:20PM +0200, Greg Kurz wrote: > The current memory accessors logic is: > - little endian if little_endian > - native endian (i.e. no byteswap) if !little_endian > > If we want to fully support cross-endian vhost, we also need to be > able to convert to big endian. > > Instead of changing the little_endian argument to some 3-value enum, this

> On Jul 10, 2015 5:29 PM, "poma via Syslinux" <syslinux at zytor.com> wrote: > > > The same as with the ISOLINUX, stable and git. > > Only this time has nothing to do with the menu. > > 1) EXTLINUX is no longer a discrete variant. The installer extlinux now > installs SYSLINUX. > 2) William Kensington already saw a similar behavior wherein an