linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: Pintu Kumar <quic_pintu@quicinc.com>,
	open list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm <linux-mm@kvack.org>,
	ebiederm@xmission.com, christian.brauner@ubuntu.com,
	sfr@canb.auug.org.au, legion@kernel.org, sashal@kernel.org,
	chris.hyser@oracle.com, ccross@google.com, pcc@google.com,
	dave@stgolabs.net, caoxiaofeng@yulong.com, david@redhat.com
Subject: Re: [PATCH] sysinfo: include availram field in sysinfo struct
Date: Thu, 6 Jan 2022 20:27:47 +0300	[thread overview]
Message-ID: <Ydcmk+WaBWKlLkAw@grain> (raw)
In-Reply-To: <CAOuPNLifYFPU4Gt2+1sOSsYNNLQq7U2aGVaYknrhaMc-CVx8vg@mail.gmail.com>

On Thu, Jan 06, 2022 at 10:19:55PM +0530, Pintu Agarwal wrote:
> > > diff --git a/include/uapi/linux/sysinfo.h b/include/uapi/linux/sysinfo.h
> > > index 435d5c2..6e77e90 100644
> > > --- a/include/uapi/linux/sysinfo.h
> > > +++ b/include/uapi/linux/sysinfo.h
> > > @@ -12,6 +12,7 @@ struct sysinfo {
> > >       __kernel_ulong_t freeram;       /* Available memory size */
> > >       __kernel_ulong_t sharedram;     /* Amount of shared memory */
> > >       __kernel_ulong_t bufferram;     /* Memory used by buffers */
> > > +     __kernel_ulong_t availram;      /* Memory available for allocation */
> > >       __kernel_ulong_t totalswap;     /* Total swap space size */
> > >       __kernel_ulong_t freeswap;      /* swap space still available */
> > >       __u16 procs;                    /* Number of current processes */
> >
> > Hi! Sorry, but I don't understand -- the sysinfo structure seems to
> > be part of user API, no? Don't we break it up here?
> 
> Yes, the corresponding user space header /usr/include/linux/sysinfo.h
> also needs to be updated.
> When we generate the kernel header it will be updated automatically.

Wait. The userspace may pass old structure here, and in result we
return incorrect layout which won't match old one, no? Old binary
code has no clue about this header update.


  reply	other threads:[~2022-01-06 17:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 15:34 Pintu Kumar
2022-01-06 16:11 ` Cyrill Gorcunov
2022-01-06 16:49   ` Pintu Agarwal
2022-01-06 17:27     ` Cyrill Gorcunov [this message]
2022-01-07 12:04       ` Christian Brauner
2022-01-07 13:44         ` Pintu Agarwal
2022-01-07 16:58           ` Vlastimil Babka
2022-01-07 17:47             ` Pintu Agarwal
2022-01-07 22:18             ` David Laight
2022-01-07 19:51         ` Cyrill Gorcunov
2022-01-06 17:41     ` David Laight
2022-01-06 17:59       ` Pintu Agarwal
2022-01-06 19:20         ` Eric W. Biederman
2022-01-07 18:07 ` [PATCH v2] " Pintu Kumar
2022-01-07 21:01   ` Cyrill Gorcunov
2022-01-08 16:24     ` Pintu Agarwal
2022-01-10  8:11       ` Cyrill Gorcunov
2022-01-07 22:22   ` David Laight
2022-01-08 16:53     ` Pintu Agarwal
2022-01-08 22:35       ` David Laight
2022-01-10 14:55         ` Pintu Agarwal

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=Ydcmk+WaBWKlLkAw@grain \
    --to=gorcunov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=caoxiaofeng@yulong.com \
    --cc=ccross@google.com \
    --cc=chris.hyser@oracle.com \
    --cc=christian.brauner@ubuntu.com \
    --cc=dave@stgolabs.net \
    --cc=david@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=legion@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pcc@google.com \
    --cc=pintu.ping@gmail.com \
    --cc=quic_pintu@quicinc.com \
    --cc=sashal@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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