From: slava@dubeyko.com
To: Deepanshu Kartikey <kartikey406@gmail.com>,
Viacheslav Dubeyko <vdubeyko@redhat.com>
Cc: konishi.ryusuke@gmail.com, linux-nilfs@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+62f0f99d2f2bb8e3bbd7@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH v3] nilfs2: reject CLEAN_SEGMENTS ioctl with out-of-range segment numbers
Date: Mon, 01 Jun 2026 09:47:43 -0700 [thread overview]
Message-ID: <9e7569ab278fc8538f0e44b552856e52f9eab37c.camel@dubeyko.com> (raw)
In-Reply-To: <CADhLXY66nCRtQk-gzHcZGm596sB2BAVKM1Ehue0ELj=OjuC-=Q@mail.gmail.com>
On Sun, 2026-05-31 at 07:14 +0530, Deepanshu Kartikey wrote:
> On Thu, Apr 30, 2026 at 11:41 PM Viacheslav Dubeyko
> <vdubeyko@redhat.com> wrote:
> >
> > Usually, I prefer to keep the err variable at the end of
> > declarations. Because,
> > it is the ending state of the function. And I am feeling that
> > something is wrong
> > every time when likewise variable is hidden inside of declaration
> > list. :) There
> > is nothing critical in my remark. But anyway... :)
> >
> > The path looks good to me.
> >
> > Thanks,
> > Slava.
> >
>
> Hi Viacheslav,
>
> Gentle Reminder. I want to know the status of the patch.
> Let me know if anything is required from my side.
>
This patch in the for-next branch several weeks already. I will send it
to upstream for 7.2-rc1 merge cycle.
Thanks,
Slava.
prev parent reply other threads:[~2026-06-01 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 4:07 Deepanshu Kartikey
2026-04-30 12:13 ` Ryusuke Konishi
2026-04-30 18:11 ` Viacheslav Dubeyko
2026-05-31 1:44 ` Deepanshu Kartikey
2026-06-01 16:47 ` slava [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=9e7569ab278fc8538f0e44b552856e52f9eab37c.camel@dubeyko.com \
--to=slava@dubeyko.com \
--cc=kartikey406@gmail.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+62f0f99d2f2bb8e3bbd7@syzkaller.appspotmail.com \
--cc=vdubeyko@redhat.com \
/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
all inboxes | Powered by JetHome®