On Nov 01, 2007 17:40 -0700, Mingming Cao wrote:
> Current journal checksumming patch failed fsstress test on NUMA. The
> bh->b_data passed to the crc32_be () function could be NULL pointer,
> which caused kernel oops immediately when running fsstress with -o
> journal_checksum. It is because t
JBD2: Fix NULL pointer bh->b_data on NUMA box with journal checksumming.
Current journal checksumming patch failed fsstress test on NUMA. The
bh->b_data passed to the crc32_be () function could be NULL pointer,
which caused kernel oops immediately when running fsstress with -o
journal_checksum.
On Thu, 2007-11-01 at 10:55 -0700, [EMAIL PROTECTED] wrote:
> The patch titled
> Forbid user to change file flags on quota files
> has been added to the -mm tree. Its filename is
> forbid-user-to-change-file-flags-on-quota-files.patch
>
> *** Remember to use Documentation/SubmitChecklis
Eric Sandeen wrote:
> Alex Tomas wrote:
>> please, try the patch attached.
>
> Looks quite a bit better:
>
> http://people.redhat.com/esandeen/seekwatcher/ext4-alex.png
> http://people.redhat.com/esandeen/seekwatcher/ext4-alex-ext4-dd-write.png
> http://people.redhat.com/esandeen/seekwatcher/ext4
The patch titled
Forbid user to change file flags on quota files
has been added to the -mm tree. Its filename is
forbid-user-to-change-file-flags-on-quota-files.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/pat
Thanks to Dave and Eric for their replies.
I'm moving the feature discussion to a higher level (pmount) and I've
opened a blueprint on it[1] with more words on why I think it's a
problem[2].
This means that I'm leaving this thread and closing it with this mail.
I would like to thank everybody wh
Alex Tomas wrote:
> please, try the patch attached.
Looks quite a bit better:
http://people.redhat.com/esandeen/seekwatcher/ext4-alex.png
http://people.redhat.com/esandeen/seekwatcher/ext4-alex-ext4-dd-write.png
http://people.redhat.com/esandeen/seekwatcher/ext4-alex-ext4-xfs-dd-write.png
It is
I just noticed this patch in the old parts of my inbox, but it was never
landed to ext3 or ext4.
- Forwarded message from Vasily Averin <[EMAIL PROTECTED]> -
Date: Mon, 04 Jun 2007 09:19:10 +0400
From: Vasily Averin <[EMAIL PROTECTED]>
To: Linux Kernel Mailing List <[EMAIL PROTECTED]>,
Jose R. Santos wrote:
> On Thu, 1 Nov 2007 06:03:00 -0500
> "Jose R. Santos" <[EMAIL PROTECTED]> wrote:
>> It seems like a problem on your end since I got the patches from the
>> mailing list after sending them. Here are the patches from the
>> archives.
>>
>> [PATCH 01/13] http://lists.openwall.n
Jose R. Santos wrote:
> On Thu, 01 Nov 2007 17:58:42 +0800
> Coly Li <[EMAIL PROTECTED]> wrote:
>
>> Coly Li wrote:
>>> I plan to do some work based on uninit group patch. When I try to patch the
>>> patch into kernel, I
>>
On Thu, 1 Nov 2007 06:03:00 -0500
"Jose R. Santos" <[EMAIL PROTECTED]> wrote:
> It seems like a problem on your end since I got the patches from the
> mailing list after sending them. Here are the patches from the
> archives.
>
> [PATCH 01/13] http://lists.openwall.net/linux-ext4/2007/10/11/20
>
On Thu, 01 Nov 2007 17:58:42 +0800
Coly Li <[EMAIL PROTECTED]> wrote:
> Coly Li wrote:
> > I plan to do some work based on uninit group patch. When I try to patch the
> > patch into kernel, I
>
> sorry
Coly Li wrote:
> I plan to do some work based on uninit group patch. When I try to patch the
> patch into kernel, I
sorry
it's typo, I mean into e2fsprogs...
> find the sequence number of patch is not c
I plan to do some work based on uninit group patch. When I try to patch the
patch into kernel, I
find the sequence number of patch is not continuous. Here is what I find for
e2fsprogs patch,
[PATCH 00/13]
[PATCH 02/13]
[PATCH 03/13]
[PATCH 04/13]
[PATCH 05/13]
[PATCH 06/13]
[PATCH 07/13]
[PATCH
14 matches
Mail list logo