linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@suse.com>
To: Jan Kara <jack@suse.cz>, Lukas Czerner <lczerner@redhat.com>
Cc: Ted Tso <tytso@mit.edu>, mwilck@suse.de, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] ext4: Avoid trim error on fs with small groups
Date: Tue, 04 Jan 2022 16:05:44 +0100	[thread overview]
Message-ID: <8bcc53097ec596bf91097aca9120dae6fcf0ef9f.camel@suse.com> (raw)
In-Reply-To: <20220104145511.u4sfkid4ltgrqlqg@quack3.lan>

On Tue, 2022-01-04 at 15:55 +0100, Jan Kara wrote:
> 
> So I think the conclusion is that we go with my original patch? Just
> I
> should update it to return computed minlen back to the user, correct?
> 
>                                                                 Honza

Yes, that's my understanding.

Martin




      reply	other threads:[~2022-01-04 15:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211112152202.26614-1-jack@suse.cz>
     [not found] ` <20211115114821.swt3nqtw2pdgahsq@work>
     [not found]   ` <20211115125141.GD23412@quack2.suse.cz>
     [not found]     ` <59b60aae9401a043f7d7cec0f8004f2ca7d4f4db.camel@suse.com>
     [not found]       ` <20211115145312.g4ptf22rl55jf37l@work>
     [not found]         ` <4e4d1ac7735c38f1395db19b97025bf411982b60.camel@suse.com>
2021-11-16 11:56           ` [PATCH] ext4: Avoid trim error on fs with small groups Lukas Czerner
2021-11-17  4:35             ` Martin K. Petersen
2021-11-19 15:43               ` Martin Wilck
2021-11-22 13:53                 ` Lukas Czerner
2022-01-03 15:34                   ` Martin Wilck
2022-01-03 18:59                     ` Lukas Czerner
2022-01-04 14:55                       ` Jan Kara
2022-01-04 15:05                         ` Martin Wilck [this message]

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=8bcc53097ec596bf91097aca9120dae6fcf0ef9f.camel@suse.com \
    --to=mwilck@suse.com \
    --cc=jack@suse.cz \
    --cc=lczerner@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mwilck@suse.de \
    --cc=tytso@mit.edu \
    /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).