linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Anton Altaparmakov <anton@tuxera.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
	Danila Chernetsov <listdansp@mail.ru>,
	"linux-ntfs-dev@lists.sourceforge.net"
	<linux-ntfs-dev@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>,
	Linux Memory Management <linux-mm@kvack.org>,
	Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
	Christian Brauner <brauner@kernel.org>
Subject: Re: ntfs orphan? (was Re: [PATCH] ntfs: do not dereference a null ctx on error)
Date: Wed, 3 May 2023 21:37:27 +0000	[thread overview]
Message-ID: <A55E04FE-2A6D-48D7-8219-77CFDDDABB0A@tuxera.com> (raw)
In-Reply-To: <20230503140609.e65bdc2b0e55ba6f49bbb620@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 2159 bytes --]

Hi,

On 3 May 2023, at 22:06, Andrew Morton <akpm@linux-foundation.org> wrote:
On Wed, 3 May 2023 11:16:02 +0700 Bagas Sanjaya <bagasdotme@gmail.com> wrote:
On Fri, Apr 07, 2023 at 07:44:33PM +0000, Danila Chernetsov wrote:
In ntfs_mft_data_extend_allocation_nolock(), if an error condition occurs
prior to 'ctx' being set to a non-NULL value, avoid dereferencing the NULL
'ctx' pointer in error handling.

Found by Linux Verification Center (linuxtesting.org) with SVACE.

Duplicate of 10-years-old outstanding patch at [1].

Well, the patches are actually quite different.  Is Danila's longer one
better?

Yes, I think the new, longer one is much nicer.  Please take that one.  Oh just noticed the next email in my inbox - you already have, thank you.

I'm not speaking of the patch itself but rather on unfortunate state
of ntfs subsystem. It seems like the maintainer is MIA (has not
responding to patch submissions for a long time). Some trivial
patches, however, are merged through mm tree.

Konstantin (from newer ntfs3 subsystem), Andrew, would you like to take a
look on this orphaned subsystem (and help reviewing)? I'd like to send
MAINTAINERS update if it turns out to be the case.


Sure, I can join linux-ntfs-dev@lists.sourceforge.net and hendle things
which come along.

Or Christian may want to do that?

Sorry, I am not totally MIA - I do handle the odd patch but I do miss many.  Sorry to say I have been so busy it is very easy for things to slip through my attention or to be read and then forgotten and my inbox is currently at 79213 messages so the old patch is probably somewhere in there just chances of me ever getting to the bottom of my inbox and dealing with all those old messages is close to zero given I am losing ground constantly rather than winning it.  I am trying just not succeeding very well...

Best regards,

Anton



[1]: https://lore.kernel.org/all/1358389709-20561-1-git-send-email-nickolai@csail.mit.edu/



--
Anton Altaparmakov <anton at tuxera.com> (replace at with @)
Lead in File System Development, Tuxera Inc., http://www.tuxera.com/
Linux NTFS maintainer


[-- Attachment #2: Type: text/html, Size: 3182 bytes --]

  reply	other threads:[~2023-05-03 21:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230407194433.25659-1-listdansp@mail.ru>
2023-05-03  4:16 ` Bagas Sanjaya
2023-05-03 21:06   ` Andrew Morton
2023-05-03 21:37     ` Anton Altaparmakov [this message]
2023-05-04 10:56     ` Christian Brauner
2023-05-05  6:17     ` Namjae Jeon

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=A55E04FE-2A6D-48D7-8219-77CFDDDABB0A@tuxera.com \
    --to=anton@tuxera.com \
    --cc=akpm@linux-foundation.org \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=bagasdotme@gmail.com \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-ntfs-dev@lists.sourceforge.net \
    --cc=listdansp@mail.ru \
    --cc=lvc-project@linuxtesting.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox