Hi,
On 6/22/07, Arnd Bergmann <[EMAIL PROTECTED]> wrote:
On Thursday 21 June 2007, Carsten Otte wrote:
>
> This is an updated version of my bugfix patch. Yan Zheng pointed out,
> that ext2_remount lacks checking if -o xip should be enabled or not.
> This patch checks for presence of
Hi,
On 6/22/07, Arnd Bergmann [EMAIL PROTECTED] wrote:
On Thursday 21 June 2007, Carsten Otte wrote:
This is an updated version of my bugfix patch. Yan Zheng pointed out,
that ext2_remount lacks checking if -o xip should be enabled or not.
This patch checks for presence of direct_access on
On Thursday 21 June 2007, Carsten Otte wrote:
>
> This is an updated version of my bugfix patch. Yan Zheng pointed out,
> that ext2_remount lacks checking if -o xip should be enabled or not.
> This patch checks for presence of direct_access on the backing block
> device and if the blocksize meets
This is an updated version of my bugfix patch. Yan Zheng pointed out,
that ext2_remount lacks checking if -o xip should be enabled or not.
This patch checks for presence of direct_access on the backing block
device and if the blocksize meets the requirements.
Andrew, please consider adding this
Yan Zheng wrote:
I mount an ext2 fs , then remount it with xip option set.
I get message below when do write operation in the fs.
Ouch. Like on mount, we should refuse -o xip on remount. The patch
below fixes this issue.
Signed-off-by: Carsten Otte <[EMAIL PROTECTED]>
---
Index:
Yan Zheng wrote:
I mount an ext2 fs , then remount it with xip option set.
I get message below when do write operation in the fs.
Ouch. Like on mount, we should refuse -o xip on remount. The patch
below fixes this issue.
Signed-off-by: Carsten Otte [EMAIL PROTECTED]
---
Index:
This is an updated version of my bugfix patch. Yan Zheng pointed out,
that ext2_remount lacks checking if -o xip should be enabled or not.
This patch checks for presence of direct_access on the backing block
device and if the blocksize meets the requirements.
Andrew, please consider adding this
On Thursday 21 June 2007, Carsten Otte wrote:
This is an updated version of my bugfix patch. Yan Zheng pointed out,
that ext2_remount lacks checking if -o xip should be enabled or not.
This patch checks for presence of direct_access on the backing block
device and if the blocksize meets the
I mount an ext2 fs , then remount it with xip option set.
I get message below when do write operation in the fs.
kernel BUG at fs/ext2/xip.c:21!
invalid opcode: [#1]
SMP
last sysfs file: /class/net/eth0/carrier
Modules linked in: ext2 autofs4 hidp rfcomm l2cap bluetooth sunrpc ipv6
I mount an ext2 fs , then remount it with xip option set.
I get message below when do write operation in the fs.
kernel BUG at fs/ext2/xip.c:21!
invalid opcode: [#1]
SMP
last sysfs file: /class/net/eth0/carrier
Modules linked in: ext2 autofs4 hidp rfcomm l2cap bluetooth sunrpc ipv6
10 matches
Mail list logo
