From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] vfs.git sysv pile
Date: Thu, 02 Mar 2023 12:31:46 +0100 [thread overview]
Message-ID: <9074146.CDJkKcVGEf@suse> (raw)
In-Reply-To: <20230302095931.jwyrlgtxcke7iwuu@quack3>
On giovedì 2 marzo 2023 10:59:31 CET Jan Kara wrote:
> On Wed 01-03-23 14:14:16, Al Viro wrote:
> > On Wed, Mar 01, 2023 at 02:00:18PM +0100, Jan Kara wrote:
> > > On Wed 01-03-23 12:20:56, Fabio M. De Francesco wrote:
> > > > On venerdì 24 febbraio 2023 04:26:57 CET Al Viro wrote:
> > > > > Fabio's "switch to kmap_local_page()" patchset (originally after the
> > > > >
> > > > > ext2 counterpart, with a lot of cleaning up done to it; as the
matter
> > > > > of
> > > > > fact, ext2 side is in need of similar cleanups - calling conventions
> > > > > there
> > > > > are bloody awful).
> > > >
> > > > If nobody else is already working on these cleanups in ext2 following
> > > > your
> > > > suggestion, I'd be happy to work on this by the end of this week. I
only
> > > > need
> > > > a confirmation because I'd hate to duplicate someone else work.
> > > >
> > > > > Plus the equivalents of minix stuff...
> > > >
> > > > I don't know this other filesystem but I could take a look and see
> > > > whether it
> > > > resembles somehow sysv and ext2 (if so, this work would be pretty
simple
> > > > too,
> > > > thanks to your kind suggestions when I worked on sysv and ufs).
> > > >
> > > > I'm adding Jan to the Cc list to hear whether he is aware of anybody
> > > > else
> > > > working on this changes for ext2. I'm waiting for a reply from you
(@Al)
> > > > or
> > > > Jan to avoid duplication (as said above).
> > >
> > > I'm not sure what exactly Al doesn't like about how ext2 handles pages
and
> > > mapping but if you have some cleanups in mind, sure go ahead. I don't
have
> > > any plans on working on that code in the near term.
> >
> > I think I've pushed a demo patchset to vfs.git at some point back in
> > January... Yep - see #work.ext2 in there; completely untested, though.
>
> OK, I think your changes to ext2_rename() in PATCH 1 leak a reference and
> mapping of old_page but otherwise I like the patches. So Fabio, if you can
> pick them up and push this to completion, it would be nice. Thanks!
>
@Jan,
I was sure you would have liked them :-)
I'm happy to pick them up and push them to completion.
But... when yesterday Al showed his demo patchset I probably interpreted his
reply the wrong way and thought that since he spent time for the demo he
wanted to put this to completion on his own.
Now I see that you are interpreting his message as an invite to use them to
shorten the time...
Furthermore I'm not sure about how I should credit him. Should I merely add a
"Suggested-by:" tag or more consistent "Co-authored-by: Al Viro <...>"? Since
he did so much I'd rather the second but I need his permission.
@Al,
Can I really proceed with *your* work? What should the better suited tag be to
credit you for the patches?
If you can reply today or at least by Friday, I'll pick your demo patchset,
put it to completion, make the patches and test them with (x)fstests on a
QEMU/KVM x86_32 bit VM, with 6GB RAM, running an HIGHMEM64GB enabled kernel.
Thanks,
Fabio
next prev parent reply other threads:[~2023-03-02 11:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 3:26 [git pull] vfs.git sysv pile Al Viro
2023-02-25 3:40 ` pr-tracker-bot
2023-03-01 11:20 ` Fabio M. De Francesco
2023-03-01 13:00 ` Jan Kara
2023-03-01 13:21 ` Fabio M. De Francesco
2023-03-01 14:14 ` Al Viro
2023-03-02 9:59 ` Jan Kara
2023-03-02 11:31 ` Fabio M. De Francesco [this message]
2023-03-02 19:35 ` Al Viro
2023-03-02 22:35 ` Al Viro
2023-03-03 5:10 ` Fabio M. De Francesco
2023-03-03 4:58 ` Fabio M. De Francesco
2023-03-08 17:40 ` Fabio M. De Francesco
2023-03-09 13:45 ` Fabio M. De Francesco
2023-03-02 19:26 ` Al Viro
2023-03-03 9:24 ` Jan Kara
2023-03-15 18:08 ` Fabio M. De Francesco
2023-03-16 9:00 ` Jan Kara
2023-03-16 10:30 ` Fabio M. De Francesco
2023-03-20 11:18 ` Fabio M. De Francesco
2023-03-20 12:47 ` Jan Kara
2023-03-27 10:29 ` Fabio M. De Francesco
2023-05-25 20:10 ` Jan Kara
2023-05-26 10:32 ` Fabio M. De Francesco
2023-05-26 13:25 ` Fabio M. De Francesco
2023-05-29 9:02 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9074146.CDJkKcVGEf@suse \
--to=fmdefrancesco@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).