public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	cem@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/9] libxfs: don't UAF a requeued EFI
Date: Mon, 27 Nov 2023 21:37:15 -0800	[thread overview]
Message-ID: <ZWV8izIb2XTOc9dJ@infradead.org> (raw)
In-Reply-To: <20231127181024.GA2766956@frogsfrogsfrogs>

On Mon, Nov 27, 2023 at 10:10:24AM -0800, Darrick J. Wong wrote:
> > It might be time to move this code into shared files?
> 
> I think Chandan started looking into what it would take to port the log
> code from the kernel into userspace.  Then xfs_trans_commit in userspace
> could actually write transactions to the log and write them back
> atomically; and xfs_repair could finally lose the -L switch.

While that does sound like a really good idea, it's now what I meant
here.  I think if we moved the actual defer ops instances out of the
_item.c files into libxfs, I think we could reuse them for the current
way of operating in userspace quite easily with strategic stubs for
some functionality.


  reply	other threads:[~2023-11-28  5:37 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 23:06 [PATCHSET 0/9] xfsprogs: minor fixes for 6.6 Darrick J. Wong
2023-11-22 23:06 ` [PATCH 1/9] libfrog: move 64-bit division wrappers to libfrog Darrick J. Wong
2023-11-23  6:34   ` Christoph Hellwig
2023-11-24  9:09   ` Chandan Babu R
2023-11-22 23:06 ` [PATCH 2/9] libxfs: don't UAF a requeued EFI Darrick J. Wong
2023-11-23  6:36   ` Christoph Hellwig
2023-11-27 18:10     ` Darrick J. Wong
2023-11-28  5:37       ` Christoph Hellwig [this message]
2023-11-28 17:01         ` Darrick J. Wong
2023-11-28 17:09           ` Christoph Hellwig
2023-11-24  9:10   ` Chandan Babu R
2023-11-22 23:07 ` [PATCH 3/9] xfs_copy: actually do directio writes to block devices Darrick J. Wong
2023-11-23  6:40   ` Christoph Hellwig
2023-11-27 18:14     ` Darrick J. Wong
2023-11-22 23:07 ` [PATCH 4/9] xfs_db: report the device associated with each io cursor Darrick J. Wong
2023-11-23  6:41   ` Christoph Hellwig
2023-11-27 18:24     ` Darrick J. Wong
2023-11-28  5:37       ` Christoph Hellwig
2023-11-22 23:07 ` [PATCH 5/9] xfs_metadump.8: update for external log device options Darrick J. Wong
2023-11-23  6:41   ` Christoph Hellwig
2023-11-24  9:11   ` Chandan Babu R
2023-11-22 23:07 ` [PATCH 6/9] xfs_mdrestore: fix uninitialized variables in mdrestore main Darrick J. Wong
2023-11-23  6:41   ` Christoph Hellwig
2023-11-24  9:11   ` Chandan Babu R
2023-11-22 23:07 ` [PATCH 7/9] xfs_mdrestore: emit newlines for fatal errors Darrick J. Wong
2023-11-23  6:41   ` Christoph Hellwig
2023-11-24  9:12   ` Chandan Babu R
2023-11-22 23:07 ` [PATCH 8/9] xfs_mdrestore: EXTERNALLOG is a compat value, not incompat Darrick J. Wong
2023-11-23  6:42   ` Christoph Hellwig
2023-11-23  6:42     ` Christoph Hellwig
2023-11-27 18:27     ` Darrick J. Wong
2023-11-28  5:38       ` Christoph Hellwig
2023-11-24  9:14   ` Chandan Babu R
2023-11-22 23:07 ` [PATCH 9/9] xfs_mdrestore: fix missed progress reporting Darrick J. Wong
2023-11-23  6:44   ` Christoph Hellwig
2023-11-24  9:14   ` Chandan Babu R

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=ZWV8izIb2XTOc9dJ@infradead.org \
    --to=hch@infradead.org \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@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