All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] misc fixes
Date: Sat, 28 Oct 2023 01:26:13 +0100	[thread overview]
Message-ID: <20231028002613.GN800259@ZenIV> (raw)

The following changes since commit 94f6f0550c625fab1f373bb86a6669b45e9748b3:

  Linux 6.6-rc5 (2023-10-08 13:49:43 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fixes

for you to fetch changes up to dc32464a5fe4946fe1a4d8f8e29961dc411933c5:

  ceph_wait_on_conflict_unlink(): grab reference before dropping ->d_lock (2023-10-27 20:14:38 -0400)

Literally nothing in common; could've been 3 separate pull requests.
All are simple regression fixes, but not for anything from this cycle.

----------------------------------------------------------------
assorted fixes all over the place

----------------------------------------------------------------
Al Viro (3):
      sparc32: fix a braino in fault handling in csum_and_copy_..._user()
      io_uring: kiocb_done() should *not* trust ->ki_pos if ->{read,write}_iter() failed
      ceph_wait_on_conflict_unlink(): grab reference before dropping ->d_lock

 arch/sparc/lib/checksum_32.S | 2 +-
 fs/ceph/mds_client.c         | 2 +-
 io_uring/rw.c                | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

             reply	other threads:[~2023-10-28  0:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-28  0:26 Al Viro [this message]
2023-10-28 18:00 ` [git pull] misc fixes pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2007-07-28 23:57 Al Viro
2007-07-29  8:11 ` Josh Triplett

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=20231028002613.GN800259@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.