doiggl | 30 Aug 13:16 2014
Picon

Here is a plain kernel based on 3.15x with the reiser4 patch enabled.

Hello,
Here is a plain kernel based on 3.15.x with the reiser4 patch built with
the Opensuse build service [obs] system.

The built rpms are here

->https://build.opensuse.org/package/binaries/home:doiggl/kernel-reiser4?repository=openSUSE_13.1
 Architecture: i586

kernel-reiser4-3.15.0-1.1.i686.rpm
kernel-reiser4-3.15.0-1.1.nosrc.rpm
kernel-reiser4-debuginfo-3.15.0-1.1.i686.rpm
kernel-reiser4-debugsource-3.15.0-1.1.i686.rpm
kernel-reiser4-devel-3.15.0-1.1.i686.rpm
kernel-reiser4-devel-debuginfo-3.15.0-1.1.i686.rpm

Repository has been published Architecture: x86_64

kernel-reiser4-3.15.0-1.1.nosrc.rpm
kernel-reiser4-3.15.0-1.1.x86_64.rpm
kernel-reiser4-debuginfo-3.15.0-1.1.x86_64.rpm
kernel-reiser4-debugsource-3.15.0-1.1.x86_64.rpm
kernel-reiser4-devel-3.15.0-1.1.x86_64.rpm
kernel-reiser4-devel-debuginfo-3.15.0-1.1.x86_64.rpm

The project is here
->https://build.opensuse.org/package/show?package=kernel-reiser4&project=home%3Adoiggl

The log of the build is here {x86_64} as an example. [Its a long buildlog]
->https://build.opensuse.org/package/live_build_log/home:doiggl/kernel-reiser4/openSUSE_13.1/x86_64
(Continue reading)

Matt | 28 Aug 17:16 2014
Picon

linux-3.16.2 queue (3.16.1+)

Hi Greg,

please consider adding the following 2 patches to 3.16.2:

Jan Kara (1):
      reiserfs: Fix use after free in journal teardown

Jeff Mahoney (1):
      reiserfs: fix corruption introduced by balance_leaf refactor

Reason/Related:

https://bugzilla.kernel.org/show_bug.cgi?id=83121

https://bugzilla.kernel.org/show_bug.cgi?id=83321

http://forums.gentoo.org/viewtopic-t-998538-postdays-0-postorder-asc-start-0.html

Many thanks in advance

Kind Regards

Matt
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

doiggl | 26 Aug 08:52 2014
Picon

What can I do next to use R4 partition sdb

Hello.
What can I do next to use R4 partition  sdb 
Thanks Glenn

- What I have done so far:

# md /media/disk

# ls -la  /media/disk
total 0
drwxr-xr-x 2 root users 48 Aug 18 16:05 .
drwxr-xr-x 4 root root  96 Aug 19 18:21 ..

mount command used.
# strace mount /dev/sdb  /media/disk

# strace shows {last few lines}
stat("/sbin/mount.reiser4", 0x7fff82b08700) = -1 ENOENT (No such file or
directory)
stat("/sbin/fs.d/mount.reiser4", 0x7fff82b08700) = -1 ENOENT (No such file
or directory)
stat("/sbin/fs/mount.reiser4", 0x7fff82b08700) = -1 ENOENT (No such file
or directory)
mount("/dev/sdb", "/media/disk", "reiser4", MS_MGC_VAL, NULL) = -1 ENOENT
(No such file or directory)
lstat("/media/disk", {st_mode=S_IFDIR|0755, st_size=48, ...}) = 0
stat("/media/disk", {st_mode=S_IFDIR|0755, st_size=48, ...}) = 0
stat("/dev/sdb", {st_mode=S_IFBLK|0660, st_rdev=makedev(8, 16), ...}) = 0
write(2, "mount: ", 7mount: )                  = 7
write(2, "mount(2) failed", 15mount(2) failed)         = 15
(Continue reading)

bugzilla-daemon | 24 Aug 15:03 2014

[Bug 83121] New: silent data corruption

https://bugzilla.kernel.org/show_bug.cgi?id=83121

            Bug ID: 83121
           Summary: silent data corruption
           Product: File System
           Version: 2.5
    Kernel Version: 3.16.1
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: ReiserFS
          Assignee: reiserfs-devel <at> vger.kernel.org
          Reporter: spike <at> ml.yaroslavl.ru
        Regression: No

In 3.16.1 kernel corrupt files in reiserfs filesystem. Data in changed files
truncated or have garbage at front. Filesystem is clean and reiserfsck found
nothing.

kernel 3.16.0 working without data loss.
kernel 3.16.1 also working on SSD drive but corrupt data on hard drive.

Data corruption detected by gentoo portage system. /usr/portage live in
reiserfs partition and updated files have incorrect checksum.

--

-- 
You are receiving this mail because:
(Continue reading)

Edward Shishkin | 24 Aug 14:04 2014
Picon

[patch 1/1] reiser4: implement ->remount_fs() super operation

Hello everyone,

This patch prevents panic during reboot/shutdown caused by VFS changes 
in 3.15

Thanks,
Edward.
doiggl | 20 Aug 09:42 2014
Picon

Which patches can be applied on top of reiser4-for-3.15.1.patch.gz

Hello,

Which patches can be applied on top of reiser4-for-3.15.1.patch.gz
2014-08-09 616.4 kB 
I see this listing[1]  [sorted by date] in
http://www.spinics.net/lists/reiserfs-devel/maillist.html
Thanks Glenn

[1] long patch listing based on date.
extracted via  # grep -i PATCHv listing.txt  | grep -i reiser4:| more

Re: [RFC] [PATCHv3 0/9] reiser4: batch discard support (FITRIM ioctl):
initial implementation.
[RFC] [PATCHv3 9/9] reiser4: batch discard support: honor minimal extent
length passed from the userspace.
[RFC] [PATCHv3 8/9] reiser4: block_alloc: add a "min_len" parameter to
reiser4_blocknr_hint to limit allocated extent length from below.
[RFC] [PATCHv3 7/9] reiser4: batch discard support: actually implement the
FITRIM ioctl handler.
[RFC] [PATCHv3 6/9] reiser4: batch discard support: add a dummy FITRIM
ioctl handler for directories.
[RFC] [PATCHv3 5/9] reiser4: txnmgr: call reiser4_post_write_back_hook()
also for empty atoms.
[RFC] [PATCHv3 4/9] reiser4: txnmgr: add reiser4_create_atom() which
creates an empty atom without capturing any nodes.
[RFC] [PATCHv3 3/9] reiser4: txnmgr: free allocated but unneeded atom in
atom_begin_and_assign_to_txnh().
[RFC] [PATCHv3 2/9] reiser4: block_alloc: add a "forward" parameter to
reiser4_blocknr_hint to allocate blocks only in forward direction.
[RFC] [PATCHv3 1/9] reiser4: block_alloc: add BA_SOME_SPACE flag for
(Continue reading)

Ivan Shapovalov | 20 Aug 00:32 2014
Picon

reiser4: porting to 3.16: any reason ->aio_read() of struct file_operations has been left out?

From `git log` I've seen that VFS people intend to replace ->aio_read() and
->aio_write() of struct file_operations with new methods ->read_iter() and
->write_iter().

(Along with a couple of related new helpers, differing from previous just in
calling _iter methods instead of aio_ ones.)

From other filesystems it seems that these are simple drop-in replacements
(however, well, I have zero familiarity with VFS). So here is a question:
is there any intentional reason that generic_file_aio_write() is not used
in reiser4?

What follows is a simple patch that I've currently applied to my own kernel
(seems to be the only significant vfs change affecting filesystems), however,
I fear that these code-paths are not generally used, so my "works for me"
isn't really representative. Could you please clarify the situation here?

From 81172835255a01718c2c256942d5887825a0cd7a Mon Sep 17 00:00:00 2001
From: Ivan Shapovalov <intelfx100 <at> gmail.com>
Date: Tue, 19 Aug 2014 14:33:35 +0400
Subject: [PATCH] Adjust reiser4 to 3.16: ->{read,write}_iter of struct
 file_operations.

1. ->aio_{read,write} of struct file_operations are being replaced with ->{read,write}_iter.
2. do_sync_{read,write} are being replaced with new_sync_{read,write}.
3. generic_file_splice_write is being replaced with iter_file_splice_write.

Signed-off-by: Ivan Shapovalov <intelfx100 <at> gmail.com>
---
 fs/reiser4/plugin/file/cryptcompress.c | 2 +-
(Continue reading)

Ivan Shapovalov | 18 Aug 16:14 2014
Picon

[PATCH 0/3] reiser4: space grabbing fixes.

These are mostly equivalent transformations (aside from the first patch)
I've done when I was experimenting with rwsems at zero-th iteration of
batch discard support.

Ivan Shapovalov (3):
  reiser4: block_alloc: improve error handling in reiser4_grab_reserved().
  reiser4: block_alloc: sanitize grab_enabled modifications.
  reiser4: do not mess with grab_enabled; instead, use BA_FORCE.

 fs/reiser4/block_alloc.c                 | 57 +++++++++++++++++---------------
 fs/reiser4/plugin/file/file.c            | 12 +++----
 fs/reiser4/plugin/file/file_conversion.c |  3 +-
 fs/reiser4/plugin/file/tail_conversion.c | 11 +++---
 fs/reiser4/plugin/item/extent_file_ops.c |  3 +-
 fs/reiser4/plugin/item/tail.c            |  3 +-
 fs/reiser4/safe_link.c                   |  4 +--
 7 files changed, 44 insertions(+), 49 deletions(-)

--

-- 
2.0.4

--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Ivan Shapovalov | 18 Aug 13:31 2014
Picon

[PATCH 0/2] reiser4: block deallocation fixes.

Actually, the idea of converting immediate allocations into deferred when
discard is enabled was flawed. Deferred deallocations ignore block stage
and additional flags, while some immediate deallocations use non-standard
stage/flags which do not match what's done by reiser4_post_write_back_hook().

So this patchset first tweaks deallocations a bit (while at it, I've
removed redundant and unused flags in some call-sites), so that immediate
deallocations for blocks that actually need to be discarded are properly
converted into deferred deallocations. Remaining instances of immediate
deallocations handle blocks which have been just allocated and not yet written
to, so they do not need to be discarded.

The second commit actually removes the wrong "conversion".

Ivan Shapovalov (2):
  reiser4: sanitize deallocations throughout the code.
  reiser4: block_alloc: get rid of discard-related hack in reiser4_dealloc_blocks().

 fs/reiser4/block_alloc.c  |  3 +--
 fs/reiser4/plugin/txmod.c | 18 ++++++------------
 fs/reiser4/tree.c         |  3 +--
 fs/reiser4/wander.c       |  5 ++---
 4 files changed, 10 insertions(+), 19 deletions(-)

--

-- 
2.0.4

--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo <at> vger.kernel.org
(Continue reading)

Ivan Shapovalov | 17 Aug 23:52 2014
Picon

[RFC] [PATCHv3 0/9] reiser4: batch discard support (FITRIM ioctl): initial implementation.

This patch series implements FITRIM ioctl support in reiser4.

The FITRIM ioctl is supposed to be applied to any directory inside the target
filesystem. At least, this can be deduced from `fstrim` utility behavior on
mainstream filesystems (e. g. ext2/3/4).

The idea of implementation is per Edward's advices: FITRIM handler iteratively
grabs a portion of disk space, sequentially allocates extents within grabbed
space and commits the resulting atom. This way we avoid starving concurrent
processes of the disk space. This process is repeated until the partition has
been fully scanned and processed.

Points I'm really uncertain of:
- grabbing fixed amount of space (new BA_SOME_SPACE flag, grabs 25% of disk space)
- creation of empty atoms (reiser4_create_atom())
- handling of empty atoms in commit_current_atom()

v2: - fix PATCH 5/7 "reiser4: txnmgr: call reiser4_post_write_back_hook() for empty atoms."
      * fix a typo
      * release atom spinlock before calling reiser4_post_write_back_hook()

v3: - use bitwise shift instead of integer division by 4 to calculate 25%
    - honor "minlen" of ioctl parameters (minimal extent length to consider for discarding)
    - fix a stupidity in reiser4_trim_fs() (two local variables holding the same superblock pointer)

Ivan Shapovalov (9):
  reiser4: block_alloc: add BA_SOME_SPACE flag for grabbing a fixed amount of space.
  reiser4: block_alloc: add a "forward" parameter to reiser4_blocknr_hint to allocate blocks only in
forward direction.
  reiser4: txnmgr: free allocated but unneeded atom in atom_begin_and_assign_to_txnh().
(Continue reading)

Ivan Shapovalov | 17 Aug 18:38 2014
Picon

Re: [RFC] [PATCH 0/7] reiser4: batch discard support (FITRIM ioctl): initial implementation.

On Sunday 17 August 2014 at 18:37:11, Dušan Čolić wrote:	
> On Aug 17, 2014 6:18 PM, "Ivan Shapovalov" <intelfx100 <at> gmail.com> wrote:
> >
> > On Sunday 17 August 2014 at 18:14:10, Dušan Čolić wrote:
> > > [...]
> > > >
> > > > Points I'm really uncertain of:
> > > > - grabbing fixed amount of space (new BA_SOME_SPACE flag, grabs 25% of
> > > disk space)
> > >
> > > Maybe grabbing 25% of remaining empty disk space would be better?
> >
> > What do you mean by "remaining"? 25% is recalculated on each iteration.
> > However, the reserved and allocated disk space is reclaimed at the end
> > of each iteration, so the amount really stays the same.
> >
> I meant not to grab 25% of whole partition size but grab amount of disk
> space equal to 25% of empty partition space so if we have only 10% of free
> space left we grab only 2.5% of it per iteration so to not get ENOSPACE if
> we used 25% of whole disk size and grabbed whole remaining disk space.

Ah. I've meant "25% of free disk space at the moment of discarding".
It's already done the correct way, I've just misworded it.

--

-- 
Ivan Shapovalov / intelfx /

> 
> > --
> > Ivan Shapovalov / intelfx /
(Continue reading)


Gmane