Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Sedat Dilek <sedat.dilek@gmail.com>, stable@vger.kernel.org
Subject: Re: [queue-6.3] Double "fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs_lookup()"
Date: Mon, 15 May 2023 05:59:06 +0200	[thread overview]
Message-ID: <2023051558-crescent-urging-a428@gregkh> (raw)
In-Reply-To: <ZGGn0IffMsXXE+lF@sashalap>

On Sun, May 14, 2023 at 11:32:32PM -0400, Sasha Levin wrote:
> On Sat, May 13, 2023 at 08:46:56PM +0200, Sedat Dilek wrote:
> > Hi,
> > 
> > while looking through 6.3-series patch-queue I noticed:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=queue/6.3&id=5a5aea218d527e82c59d0164b4205a96399bda8e
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=queue/6.3&id=a5085c4040ae421cc5d90bba2a1a1cecd6f800c0
> > 
> > Looks like the same patch:
> > 
> > fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs_lookup()
> > commit 254e69f284d7270e0abdc023ee53b71401c3ba0c upstream.
> > 
> > fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs_lookup()
> > [ Upstream commit 254e69f284d7270e0abdc023ee53b71401c3ba0c ]
> 
> Looks like Greg's patch somehow applied on top of mine, I've dropped it.

Thank you, this got confusing fast...

      reply	other threads:[~2023-05-15  3:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-13 18:46 [queue-6.3] Double "fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs_lookup()" Sedat Dilek
2023-05-15  3:32 ` Sasha Levin
2023-05-15  3:59   ` Greg Kroah-Hartman [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=2023051558-crescent-urging-a428@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=sashal@kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=stable@vger.kernel.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