All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: Christian Brauner <brauner@kernel.org>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Anton Altaparmakov <anton@tuxera.com>,
	Namjae Jeon <linkinjeon@kernel.org>,
	ntfs3@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	linux-ntfs-dev@lists.sourceforge.net,
	regressions@lists.linux.dev
Subject: Re: [PATCH 2/2] ntfs3: remove warning
Date: Thu, 18 Apr 2024 08:36:21 +0200	[thread overview]
Message-ID: <ZiC_ZQcIjM3xv3zT@hovoldconsulting.com> (raw)
In-Reply-To: <015aa42b-abac-4810-8743-43913ab8e2d9@paragon-software.com>

On Wed, Apr 17, 2024 at 07:07:06PM +0300, Konstantin Komarov wrote:
> On 25.03.2024 11:34, Christian Brauner wrote:
> > This causes visible changes for users that rely on ntfs3 to serve as an
> > alternative for the legacy ntfs driver. Print statements such as this
> > should probably be made conditional on a debug config option or similar.

> The initial and true reason for multiple warnings is the disregard of 
> short (DOS) names when counting hard links.
> 
> This patch should fixes this bug:
> https://lore.kernel.org/ntfs3/0cb0b314-e4f6-40a2-9628-0fe7d905a676@paragon-software.com/T/#u

As I just replied in that thread, I'm also seeing link counts being
reduced from 3 to 1, that is, to not just be decremented by one due to
the DOS name bug.

Are you sure there are no further issues here and that the patch is
indeed correct?

I did not test the patch, which is white-space damaged, but if it
addresses also the remaining warnings then the commit message would need
to be updated as well.

Johan

      reply	other threads:[~2024-04-18  6:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15  7:20 [PATCH] fs: Remove NTFS classic Matthew Wilcox (Oracle)
2024-01-15 11:00 ` Anton Altaparmakov
2024-01-15 11:08   ` Enrico Mioso
2024-01-15 11:41   ` Namjae Jeon
2024-01-15 14:49   ` Matthew Wilcox
2024-01-16  9:52     ` [PATCH] " Anton Altaparmakov
2024-01-15 22:20 ` [PATCH] fs: " Dave Chinner
2024-01-16  9:33 ` Christian Brauner
2024-01-16  9:51   ` [PATCH] " Anton Altaparmakov
2024-01-16 11:06     ` Christian Brauner
2024-01-16 11:32       ` Anton Altaparmakov
2024-03-22 16:35   ` [PATCH] fs: " Johan Hovold
2024-03-25  8:28     ` Christian Brauner
2024-03-25  8:34     ` [PATCH 1/2] ntfs3: serve as alias for the legacy ntfs driver Christian Brauner
2024-03-25 10:09       ` Johan Hovold
2024-03-25 12:01         ` Christian Brauner
2024-03-25  8:34     ` [PATCH 2/2] ntfs3: remove warning Christian Brauner
2024-03-25 10:12       ` Johan Hovold
2024-03-25 12:05         ` Christian Brauner
2024-04-04  8:06           ` Linux regression tracking (Thorsten Leemhuis)
2024-04-11 11:03             ` Konstantin Komarov
2024-04-15  9:54               ` Johan Hovold
2024-04-15 10:20                 ` Johan Hovold
2024-04-15 11:32                   ` Anton Altaparmakov
2024-04-15 11:42                     ` Johan Hovold
2024-04-15 14:15                       ` Christian Brauner
2024-04-15 15:23                         ` Linus Torvalds
2024-04-15 15:27                           ` Matthew Wilcox
2024-04-15 15:47                           ` Johan Hovold
2024-04-15 15:51                             ` Linus Torvalds
2024-04-15 16:06                               ` Johan Hovold
2024-04-16 10:38                                 ` Christian Brauner
2024-04-16 12:55                                   ` Johan Hovold
2024-04-17 16:07       ` Konstantin Komarov
2024-04-18  6:36         ` Johan Hovold [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=ZiC_ZQcIjM3xv3zT@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=anton@tuxera.com \
    --cc=brauner@kernel.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-ntfs-dev@lists.sourceforge.net \
    --cc=ntfs3@lists.linux.dev \
    --cc=regressions@lists.linux.dev \
    --cc=willy@infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.