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, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git misc pile
Date: Mon, 12 Dec 2022 00:39:32 +0000	[thread overview]
Message-ID: <Y5Z4RCCOiu1OrmS2@ZenIV> (raw)

The last commit in there (sysvfs very belated fix) had been there only
since Friday, but it's a really obvious fix - the bug had been introduced
in minixfs and sysvfs in 2002, minixfs got caught and fixed 2 years later
and sysvfs one got missed.  Fix is the same one-liner.  Up to you...

The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:

  Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)

are available in the Git repository at:

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

for you to fetch changes up to e0c49bd2b4d3cd1751491eb2d940bce968ac65e9:

  fs: sysv: Fix sysv_nblocks() returns wrong value (2022-12-10 14:13:37 -0500)

----------------------------------------------------------------
misc pile

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

----------------------------------------------------------------
Chen Zhongjin (1):
      fs: sysv: Fix sysv_nblocks() returns wrong value

Christoph Hellwig (1):
      fs: simplify vfs_get_super

Jeff Layton (1):
      fs: drop useless condition from inode_needs_update_time

Zhen Lei (2):
      btrfs: replace INT_LIMIT(loff_t) with OFFSET_MAX
      get rid of INT_LIMIT, use type_max() instead

 Documentation/filesystems/mount_api.rst | 11 ------
 fs/btrfs/ordered-data.c                 |  6 ++--
 fs/inode.c                              |  3 --
 fs/super.c                              | 60 +++++----------------------------
 fs/sysv/itree.c                         |  2 +-
 include/linux/fs.h                      |  5 ++-
 include/linux/fs_context.h              | 14 --------
 7 files changed, 15 insertions(+), 86 deletions(-)

             reply	other threads:[~2022-12-12  0:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12  0:39 Al Viro [this message]
2022-12-13  3:49 ` [git pull] vfs.git misc pile pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2023-04-24  4:29 Al Viro
2023-04-25  2:49 ` pr-tracker-bot
2024-01-11 10:21 Al Viro
2024-01-12  5:07 ` pr-tracker-bot

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=Y5Z4RCCOiu1OrmS2@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --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.